From: Zhang Rui <rui.zhang@intel.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Len Brown <lenb@kernel.org>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI: event: fix acpi_bus_generate_netlink_event call
Date: Tue, 04 Sep 2007 08:56:38 +0800 [thread overview]
Message-ID: <1188867398.3082.305.camel@acpi-hp.sh.intel.com> (raw)
In-Reply-To: <20070903230642.GB3899@khazad-dum.debian.net>
On Mon, 2007-09-03 at 20:06 -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 03 Sep 2007, Len Brown wrote:
> > Wow, do you really build with CONFIG_NET=n,
> > or did randconfig find this?
>
> My build-it-quick config for thinkpad-acpi has CONFIG_NET=n :-)
>
> It is not a kernel I use to test anything but straight "does it even
> compile?", though...
>
Oops, thanks for fixing this.
Rui
prev parent reply other threads:[~2007-09-04 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 3:03 [PATCH] ACPI: event: fix acpi_bus_generate_netlink_event call Henrique de Moraes Holschuh
2007-09-03 20:59 ` Len Brown
2007-09-03 23:06 ` Henrique de Moraes Holschuh
2007-09-04 0:56 ` Zhang Rui [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=1188867398.3082.305.camel@acpi-hp.sh.intel.com \
--to=rui.zhang@intel.com \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@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