public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] ACPI: Remove unused struct acpi_pci_root.id member
Date: Thu, 20 Dec 2012 22:20:15 +0100	[thread overview]
Message-ID: <4397899.8xnBDh90Bg@vostro.rjw.lan> (raw)
In-Reply-To: <CAErSpo5oFEa5RD1_EYLtwvwF0dZFpkUp9XqO_kJZ+c5bL-1TTw@mail.gmail.com>

On Thursday, December 20, 2012 11:37:24 AM Bjorn Helgaas wrote:
> On Wed, Dec 19, 2012 at 6:22 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Wednesday, December 19, 2012 10:30:44 AM Bjorn Helgaas wrote:
> >> This member is never initialized and never referenced, so remove it.
> >
> > Sure. :-)
> >
> > Do you want me to take this?
> 
> I assume you're going to push your namespace scan rework through your
> tree, since most of the changes are in drivers/acpi.  That series also
> touches acpi_bus.h, so probably makes the most sense for you to take
> this as well.  I don't plan any future changes to the file.

Well, I'm not planning to push the scan rework series for v3.8, I'd rather
prefer it to go into v3.9.  I'll just create a separate branch based on
v3.8-rc1 with those patches that will wait for the v3.9 merge window and
can be pulled from if necessary.

I can put the $subject patch into that branch too.

Does it sound reasonable?

> There are more PCI-centric pci_root.c changes in the pipe, but we'll
> have to sort those out later, I think.

Yup.

> Let me know if you think otherwise.

The above is fine by me.

> >> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> >> ---
> >>  include/acpi/acpi_bus.h |    1 -
> >>  1 files changed, 0 insertions(+), 1 deletions(-)
> >>
> >> diff --git a/include/acpi/acpi_bus.h b/include/acpi/acpi_bus.h
> >> index 7ced5dc..4f42c0e 100644
> >> --- a/include/acpi/acpi_bus.h
> >> +++ b/include/acpi/acpi_bus.h
> >> @@ -397,7 +397,6 @@ int unregister_acpi_bus_type(struct acpi_bus_type *);
> >>  struct acpi_pci_root {
> >>       struct list_head node;
> >>       struct acpi_device * device;
> >> -     struct acpi_pci_id id;
> >>       struct pci_bus *bus;
> >>       u16 segment;
> >>       struct resource secondary;      /* downstream bus range */
> >>
> > --
> > I speak only for myself.
> > Rafael J. Wysocki, Intel Open Source Technology Center.
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2012-12-20 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 17:30 [PATCH] ACPI: Remove unused struct acpi_pci_root.id member Bjorn Helgaas
2012-12-20  1:22 ` Rafael J. Wysocki
2012-12-20 18:37   ` Bjorn Helgaas
2012-12-20 21:20     ` Rafael J. Wysocki [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=4397899.8xnBDh90Bg@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@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