From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Krzysztof Wilczy??ski <kw@linux.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Dan Williams <dan.j.williams@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Kees Cook <keescook@chromium.org>, Pali Roh??r <pali@kernel.org>,
Oliver O'Halloran <oohall@gmail.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 2/2] PCI/sysfs: Pass iomem_get_mapping() as a function pointer
Date: Mon, 28 Jun 2021 13:09:06 +0200 [thread overview]
Message-ID: <YNmt0gkonSbCXxus@kroah.com> (raw)
In-Reply-To: <20210628102453.GA139153@rocinante>
On Mon, Jun 28, 2021 at 12:24:53PM +0200, Krzysztof Wilczy??ski wrote:
> Hi Christoph,
>
> > Doesn't this need to be merged into the previous patch to prevent
> > a compile failure after just the previous patch is applied?
>
> Yes, it does. I kept it separate for the sake of review, since we have
> sysfs and PCI involved. I wasn't sure if Bjorn would prefer to have
> this done as separate patches or not, to be honest.
>
> Bjorn said that he can squash this when applying, thus I left it as-is
> for now - which means that the entire series has to be applied for
> everything to build cleanly.
>
> I will send v3 that merges first two patches. Sorry for troubles!
This all needs to wait until after 5.14-rc1 is out anyway, so no rush.
greg k-h
prev parent reply other threads:[~2021-06-28 11:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 23:31 [PATCH 0/2] Allow deferred execution of iomem_get_mapping() Krzysztof Wilczyński
2021-06-25 23:31 ` [PATCH 1/2] sysfs: Invoke iomem_get_mapping() from the sysfs open callback Krzysztof Wilczyński
2021-06-25 23:53 ` Dan Williams
2021-06-28 10:09 ` Christoph Hellwig
2021-06-28 10:41 ` Krzysztof Wilczy??ski
2021-06-28 17:36 ` Dan Williams
2021-06-28 18:06 ` Krzysztof Wilczyński
2021-06-28 18:29 ` Dan Williams
2021-06-25 23:31 ` [PATCH 2/2] PCI/sysfs: Pass iomem_get_mapping() as a function pointer Krzysztof Wilczyński
2021-06-25 23:56 ` Dan Williams
2021-06-26 13:07 ` Krzysztof Wilczyński
2021-06-28 10:15 ` Christoph Hellwig
2021-06-28 10:24 ` Krzysztof Wilczy??ski
2021-06-28 11:09 ` Greg Kroah-Hartman [this message]
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=YNmt0gkonSbCXxus@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=hch@infradead.org \
--cc=keescook@chromium.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=oohall@gmail.com \
--cc=pali@kernel.org \
/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