From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6E34613D257; Wed, 27 Mar 2024 13:34:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711546488; cv=none; b=JauUuAQu/M+/408e+aJRISYbM4gG2kN4vMJAehO5KFeYgUg/vImlaFCLxZDMl19G1xh6Q1x/F5ard8LVV5N/509CiqhEIrQ0JgXX7tI5WpAl78i7TpwW7RMw1lqQehsOh4CJ1f+RYmyCRIu7BXRKwVdm2+mJcwa12hVIL+dYsbU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711546488; c=relaxed/simple; bh=NZdy0X3liUqTEzRbInNe/vjDY6MNb1re1WUM40McVv8=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=LZ8Dln/zjOG72JEUOOS4hbQGPyqejul50l9nbRk1O9/j/Rfqp6RIUUwou18pshvK4NOIXs3J3ok3RAbi8dNC3PJur9gY/y88nXRfR7ArgDBrTakRHToQNEh89L2/kX4IQu3z6HSRuFamam4r/nlwqILxX7Is51TInAIiy4EKT8Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=fntl9GJN; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="fntl9GJN" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=NZdy0X3liUqTEzRbInNe/vjDY6MNb1re1WUM40McVv8=; t=1711546486; x=1712756086; b=fntl9GJNw3T27S/XWxW9sEjOSV4SmrZcmhhd4YlmpmHI4Iq mnOniwoR0IVjm9aWq+CRox56fWuhkne7MyGhcdaJ/k9N0CamgZPzcOV6zRF/pIndpPcw9Avuee9/t Si10y0HmSlsxIerM6wXTBAQ/Rpd4MzPYYamUefqKMbXXytKdsw7G9N4p3a6Sra2uAATsNm1DhnV2I /NO/SWUAN3iibTqe88eFukUDg6Zavwqp5anj0M1kJLYbYvKFNJKYt3LTnAYA6SoJQykU8Q/kZ0mAm 44zBsq7XBJ5QEBZqb6eJqoEbgQY27FyoA4YurKsX7p0fIloHRjrexNCFUtwOY0QQ==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.97) (envelope-from ) id 1rpTPq-0000000H6pw-3l9Q; Wed, 27 Mar 2024 14:34:07 +0100 Message-ID: <46e9539f59c82762e3468a9519fa4123566910d5.camel@sipsolutions.net> Subject: Re: [PATCH 02/22] um: virt-pci: drop owner assignment From: Johannes Berg To: Krzysztof Kozlowski , "Michael S. Tsirkin" , Jason Wang , Xuan Zhuo , Richard Weinberger , Anton Ivanov , Paolo Bonzini , Stefan Hajnoczi , Jens Axboe , Marcel Holtmann , Luiz Augusto von Dentz , Olivia Mackall , Herbert Xu , Amit Shah , Arnd Bergmann , Greg Kroah-Hartman , Gonglei , "David S. Miller" , Viresh Kumar , Linus Walleij , Bartosz Golaszewski , David Airlie , Gerd Hoffmann , Gurchetan Singh , Chia-I Wu , Jean-Philippe Brucker , Joerg Roedel , Alexander Graf , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Eric Van Hensbergen , Latchesar Ionkov , Dominique Martinet , Christian Schoenebeck , Stefano Garzarella , Kalle Valo , Dan Williams , Vishal Verma , Dave Jiang , Ira Weiny , Pankaj Gupta , Bjorn Andersson , Mathieu Poirier , "Martin K. Petersen" , Vivek Goyal , Miklos Szeredi , Anton Yakovlev , Jaroslav Kysela , Takashi Iwai Cc: virtualization@lists.linux.dev, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-um@lists.infradead.org, linux-block@vger.kernel.org, linux-bluetooth@vger.kernel.org, linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org, dri-devel@lists.freedesktop.org, iommu@lists.linux.dev, netdev@vger.kernel.org, v9fs@lists.linux.dev, kvm@vger.kernel.org, linux-wireless@vger.kernel.org, nvdimm@lists.linux.dev, linux-remoteproc@vger.kernel.org, linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org, alsa-devel@alsa-project.org, linux-sound@vger.kernel.org Date: Wed, 27 Mar 2024 14:34:04 +0100 In-Reply-To: <20240327-module-owner-virtio-v1-2-0feffab77d99@linaro.org> References: <20240327-module-owner-virtio-v1-0-0feffab77d99@linaro.org> <20240327-module-owner-virtio-v1-2-0feffab77d99@linaro.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.50.4 (3.50.4-1.fc39) Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Wed, 2024-03-27 at 13:40 +0100, Krzysztof Kozlowski wrote: > virtio core already sets the .owner, so driver does not need to. > All further patches depend on the first virtio patch, therefore please ac= k > 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