Re: [PATCH 02/22] um: virt-pci: drop owner assignment
From: Krzysztof Kozlowski <krzk@kernel.org>
Date: 2024-03-27 13:40:58
Also in:
alsa-devel, dri-devel, kvm, linux-block, linux-bluetooth, linux-crypto, linux-doc, linux-fsdevel, linux-gpio, linux-iommu, linux-remoteproc, linux-scsi, linux-sound, linux-um, linux-wireless, lkml, nvdimm, v9fs, virtualization
On 27/03/2024 14:34, Johannes Berg wrote:
On Wed, 2024-03-27 at 13:40 +0100, Krzysztof Kozlowski wrote:quoted
virtio core already sets the .owner, so driver does not need to.quoted
All further patches depend on the first virtio patch, therefore please ack and this should go via one tree: virtio?Sure. Though it's not really actually necessary, you can set it in the core and merge the other patches in the next cycle; those drivers that _have_ an .owner aren't broken after all. Acked-by: Johannes Berg <johannes@sipsolutions.net>
True, this can be spread over two cycles. What I wanted to express, is that maintainers should not pick individual patches. Thanks for the Ack and apologies for a bit too big CC-list. I need to learn how to ask b4 to make Cc-per-patch for such case. Best regards, Krzysztof