From: Bjorn Helgaas <bhelgaas@google.com>
To: dave@gnu.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Len Brown <lenb@kernel.org>,
linux-pci@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 3/5] PCI: hotplug: remove acpi_bus_generate_proc_event
Date: Mon, 10 Sep 2012 16:54:19 -0600 [thread overview]
Message-ID: <CAErSpo7FAZvpWvhYCPUL8X1LBKmArUg3BYuCthwcKTeHR4nu+w@mail.gmail.com> (raw)
In-Reply-To: <1346630607.3170.31.camel@offbook>
On Sun, Sep 2, 2012 at 6:03 PM, Davidlohr Bueso <dave@gnu.org> wrote:
> Calling this function no longer makes sense as /proc/acpi/event
> is being removed.
>
> Signed-off-by: Davidlohr Bueso <dave@gnu.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
I assume this series will be applied as a group somewhere other than
the PCI tree. Let me know if you need me to do anything more than ack
this one.
> ---
> drivers/pci/hotplug/acpiphp_ibm.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/hotplug/acpiphp_ibm.c b/drivers/pci/hotplug/acpiphp_ibm.c
> index c35e8ad..5394fff 100644
> --- a/drivers/pci/hotplug/acpiphp_ibm.c
> +++ b/drivers/pci/hotplug/acpiphp_ibm.c
> @@ -270,7 +270,6 @@ static void ibm_handle_events(acpi_handle handle, u32 event, void *context)
>
> if (subevent == 0x80) {
> dbg("%s: generationg bus event\n", __func__);
> - acpi_bus_generate_proc_event(note->device, note->event, detail);
> acpi_bus_generate_netlink_event(note->device->pnp.device_class,
> dev_name(¬e->device->dev),
> note->event, detail);
> --
> 1.7.4.1
>
>
>
>
prev parent reply other threads:[~2012-09-10 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 0:03 Davidlohr Bueso
2012-09-10 22:54 ` Bjorn Helgaas [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=CAErSpo7FAZvpWvhYCPUL8X1LBKmArUg3BYuCthwcKTeHR4nu+w@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=akpm@linux-foundation.org \
--cc=dave@gnu.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®