From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-scsi@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Jakub Kicinski <kuba@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org,
Khalid Aziz <khalid@gonehiking.org>,
"Maciej W . Rozycki" <macro@orcam.me.uk>,
Matt Wang <wwentao@vmware.com>,
Miquel van Smoorenburg <mikevs@xs4all.net>,
Mark Salyzyn <salyzyn@android.com>,
linuxppc-dev@lists.ozlabs.org, linux-arch@vger.kernel.org,
linux-alpha@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-parisc@vger.kernel.org, Denis Efremov <efremov@linux.com>
Subject: Re: [PATCH v3 0/3] phase out CONFIG_VIRT_TO_BUS
Date: Mon, 27 Jun 2022 22:59:08 -0400 [thread overview]
Message-ID: <yq1bkudh4va.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220624155226.2889613-1-arnd@kernel.org> (Arnd Bergmann's message of "Fri, 24 Jun 2022 17:52:23 +0200")
Hi Arnd!
> If there are no more issues identified with this series, I'll merge it
> through the asm-generic tree. The SCSI patches can also get merged
> separately through the SCSI maintainers' tree if they prefer.
I put patches 1 and 2 in scsi-staging to see if anything breaks...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-06-28 2:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 15:52 [PATCH v3 0/3] phase out CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-24 15:52 ` [PATCH v3 1/3] scsi: BusLogic remove bus_to_virt Arnd Bergmann
2022-06-24 16:38 ` Khalid Aziz
2022-06-24 15:52 ` [PATCH v3 3/3] arch/*/: remove CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-26 9:39 ` Helge Deller
2022-06-24 17:08 ` [PATCH v3 0/3] phase out CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-28 2:59 ` Martin K. Petersen [this message]
2022-06-28 11:31 ` Arnd Bergmann
2022-07-07 21:47 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq1bkudh4va.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=efremov@linux.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=khalid@gonehiking.org \
--cc=kuba@kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=macro@orcam.me.uk \
--cc=mikevs@xs4all.net \
--cc=robin.murphy@arm.com \
--cc=salyzyn@android.com \
--cc=wwentao@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox