Linux kernel -stable discussions
 help / color / mirror / Atom feed
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 10:19:25 +0200	[thread overview]
Message-ID: <YRYrDQ3yuvtLtoKr@kroah.com> (raw)
In-Reply-To: <20210812171450.GA2485383@bjorn-Precision-5520>

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?

> That would make my v5.15 pull request easier because I simple-mindedly
> base all my branches on -rc1 while your branch is based on -rc3.  But
> again, up to you.  I put those two patches on a local branch:
> 
>   94b34bc04c25 ("sysfs: Rename struct bin_attribute member to f_mapping")
>   97e9dada53f1 ("sysfs: Invoke iomem_get_mapping() from the sysfs open callback")
> 
> in case that seems better to you.

I do not see what I can do with that here as it's already in my tree :(

confused,

greg k-h

  reply	other threads:[~2021-08-13  8:19 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 [this message]
2021-08-13 14:29       ` Bjorn Helgaas
2021-08-13 15:09         ` Greg Kroah-Hartman
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=YRYrDQ3yuvtLtoKr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox