From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Dan Williams" <dan.j.williams@intel.com>,
"Sasha Levin" <sashal@kernel.org>,
linux-pci@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] PCI/sysfs: Use correct variable for the legacy_mem sysfs object
Date: Fri, 13 Aug 2021 17:09:37 +0200 [thread overview]
Message-ID: <YRaLMWh3zsVQqNr1@kroah.com> (raw)
In-Reply-To: <20210813142901.GA2574831@bjorn-Precision-5520>
On Fri, Aug 13, 2021 at 09:29:01AM -0500, Bjorn Helgaas wrote:
> On Fri, Aug 13, 2021 at 10:19:25AM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Aug 12, 2021 at 12:14:50PM -0500, Bjorn Helgaas wrote:
> > > On Thu, Aug 12, 2021 at 11:17:12AM -0500, Bjorn Helgaas wrote:
> > > > [+to Greg, please update sysfs_defferred_iomem_get_mapping-5.15]
> > >
> > > Actually, Greg, totally up to you, but if nobody else is depending on
> > > the sysfs_defferred_iomem_get_mapping-5.15 branch, another possibility
> > > would be for you to drop that branch and for me to merge the two
> > > patches on it + Krzysztof's fix below + (hopefully) Krzysztof's PCI
> > > static attribute work.
> >
> > I can not "drop" the branch as it is already merged into my
> > driver-core-next branch that I can not rebase. I could revert it, but
> > is that really needed?
>
> Nope, I don't think a revert is warranted. I'll take care of getting
> Krzysztof's fix into v5.15.
Thanks, I'll handle the merge issues after that happens in my tree.
greg k-h
next prev parent reply other threads:[~2021-08-13 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 13:21 [PATCH] PCI/sysfs: Use correct variable for the legacy_mem sysfs object Krzysztof Wilczyński
2021-08-12 16:17 ` Bjorn Helgaas
2021-08-12 17:14 ` Bjorn Helgaas
2021-08-13 8:19 ` Greg Kroah-Hartman
2021-08-13 14:29 ` Bjorn Helgaas
2021-08-13 15:09 ` Greg Kroah-Hartman [this message]
2021-08-13 7:23 ` Daniel Vetter
2021-08-19 15:25 ` Bjorn Helgaas
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=YRaLMWh3zsVQqNr1@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.