From: Greg KH <gregkh@linuxfoundation.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Joseph Salisbury <joseph.salisbury@canonical.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] PCI: pcibus address to resource converting take bus instead of dev
Date: Mon, 9 Dec 2013 12:43:23 -0800 [thread overview]
Message-ID: <20131209204323.GA25180@kroah.com> (raw)
In-Reply-To: <CAE9FiQUrTAnQkiS9SU3-pJ35-U9CqXQNQEceUUarf-WiPXCF2Q@mail.gmail.com>
On Mon, Dec 09, 2013 at 12:03:18PM -0800, Yinghai Lu wrote:
> On Mon, Dec 9, 2013 at 11:21 AM, Yinghai Lu <yinghai@kernel.org> wrote:
> > On Mon, Dec 9, 2013 at 9:52 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> >>
> >> Ugh. Why would we add new functions with "__" prefixes? There are
> >> only a handful of callers to pcibios_bus_to_resource() and
> >> pcibios_resource_to_bus(). We can just change them to supply a
> >> "struct pci_bus *" directly. That's a better match for how the
> >> hardware works anyway.
> >
>
> Please double check if you are happy with the change.
> Hope that will not update stable tree maintainer guys.
What do you mean by this?
How is this a -stable kernel patch?
next prev parent reply other threads:[~2013-12-09 20:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:54 [PATCH 0/2] PCI: Don't enable realloc automatically when above 4g 64bit mmio is not supported Yinghai Lu
2013-12-08 23:54 ` [PATCH 1/2] PCI: pcibus address to resource converting take bus instead of dev Yinghai Lu
2013-12-09 17:52 ` Bjorn Helgaas
2013-12-09 19:21 ` Yinghai Lu
2013-12-09 20:03 ` Yinghai Lu
2013-12-09 20:43 ` Greg KH [this message]
2013-12-09 20:47 ` Yinghai Lu
2013-12-09 21:06 ` Bjorn Helgaas
2013-12-08 23:54 ` [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio Yinghai Lu
2013-12-09 17:54 ` Bjorn Helgaas
2013-12-09 19:20 ` Yinghai Lu
2013-12-09 19:42 ` Bjorn Helgaas
2013-12-09 20:10 ` Yinghai Lu
2013-12-09 20:20 ` Bjorn Helgaas
2013-12-09 20:44 ` Yinghai Lu
2013-12-09 21:05 ` Bjorn Helgaas
2013-12-11 19:19 ` Joseph Salisbury
2013-12-11 19:55 ` Yinghai Lu
2014-01-08 16:38 ` Joseph Salisbury
2014-01-10 16:19 ` Joseph Salisbury
2014-01-10 17:13 ` Yinghai Lu
2014-01-10 21:54 ` Joseph Salisbury
2014-01-10 23:12 ` Yinghai Lu
2014-09-16 20:21 ` Joseph Salisbury
2014-09-16 22:27 ` Yinghai Lu
2014-09-17 7:46 ` Yinghai Lu
2014-09-24 23:48 ` Bjorn Helgaas
2014-09-25 18:19 ` Joseph Salisbury
2014-09-25 18:24 ` Yinghai Lu
2014-09-25 15:49 ` Joseph Salisbury
2014-09-25 16:04 ` Bjorn Helgaas
2014-09-25 18:04 ` Joseph Salisbury
2014-09-25 18:23 ` Yinghai Lu
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=20131209204323.GA25180@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yinghai@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.