public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Len Brown <lenb@kernel•org>,
	"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
	"Zhang, Rui" <rui.zhang@intel•com>
Subject: Re: linux-next: acpi tree build failure
Date: Wed, 15 Oct 2008 13:15:26 +0800	[thread overview]
Message-ID: <20081015051526.GA25322@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20081015160837.71912a6d.sfr@canb.auug.org.au>

On Wed, Oct 15, 2008 at 01:08:37PM +0800, Stephen Rothwell wrote:
> Hi Len,
> 
> Today's linux-next build (x86_64 allmodconfig) failed like this:
> 
> ERROR: "acpi_os_hotplug_execute" [drivers/acpi/dock.ko] undefined!
> 
> Caused by commit 19cd847ab24fefe9e50101ec94479e0400a08650 ("ACPI: fix
> hotplug race").  I added the patch below.
We need make dock driver not a module.

Len,
please check your mail box, I had sent the patch (make dock driver built-int) to you before.

Thanks,
Shaohua

  reply	other threads:[~2008-10-15  5:16 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15  5:08 linux-next: acpi tree build failure Stephen Rothwell
2008-10-15  5:15 ` Shaohua Li [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-14  1:20 Stephen Rothwell
2009-12-14 19:20 ` Bjorn Helgaas
2009-12-15  4:57 ` Bjorn Helgaas
2009-12-15 22:37   ` Len Brown
2009-12-15 23:28     ` Stephen Rothwell
2009-12-16  2:28     ` Stephen Rothwell
2009-09-26  2:15 Stephen Rothwell
2009-09-26  3:11 ` Bjorn Helgaas
2009-09-27  1:27   ` Crane Cai
2009-09-27  7:54     ` Len Brown
2009-09-01  2:57 Stephen Rothwell
2009-09-07 13:46 ` Stephen Rothwell
2009-09-08  0:47   ` Zhang Rui
2009-09-09  4:02     ` Len Brown
2009-09-09  5:45       ` Stephen Rothwell
2009-06-30  3:16 Stephen Rothwell
2009-07-06  6:18 ` Stephen Rothwell
2009-07-07  3:17 ` Len Brown
2009-07-07  3:53   ` Stephen Rothwell
2009-04-24  4:46 Stephen Rothwell
2009-04-24 15:15 ` Len Brown
2009-03-18  0:57 Stephen Rothwell
2009-03-18  1:09 ` Lin Ming
2009-03-18  3:27   ` Stephen Rothwell
2009-03-27 20:49     ` Len Brown
2009-02-24  4:37 Stephen Rothwell
2009-03-03  1:47 ` Stephen Rothwell
2009-03-16  5:10   ` Stephen Rothwell
2009-03-27 20:58   ` Len Brown
2009-02-02  2:22 Stephen Rothwell
2009-02-05  2:13 ` Stephen Rothwell
2009-02-05  5:00   ` Greg KH
2009-02-07  4:06     ` Len Brown
2009-02-07  5:32       ` Greg KH
2008-10-15  4:51 Stephen Rothwell
2008-08-12  3:16 Stephen Rothwell
2008-08-12  7:06 ` Andi Kleen
2008-08-12 20:07   ` Carlos Corbacho
2008-08-12 21:29 ` Carlos Corbacho

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=20081015051526.GA25322@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel$(echo .)com \
    --cc=lenb@kernel$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rui.zhang@intel$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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