[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A5ED84D3BB3A384992CBB9C77DEDA4D414A3D7E4@USINDEM103.corp.hds.com>
Date: Thu, 10 Jan 2013 23:58:53 +0000
From: Seiji Aguchi <seiji.aguchi@....com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
"Luck, Tony" <tony.luck@...el.com>
CC: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: linux-next: build failure after merge of the ia64 tree
Stephen, Tony,
I will take a look at it.
Seiji
> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@...b.auug.org.au]
> Sent: Thursday, January 10, 2013 6:55 PM
> To: Luck, Tony
> Cc: linux-next@...r.kernel.org; linux-kernel@...r.kernel.org; Seiji Aguchi
> Subject: linux-next: build failure after merge of the ia64 tree
>
> Hi all,
>
> After merging the ia64 tree, today's linux-next build (x86_64_allmodconfig) failed like this:
>
> ERROR: "pstore_cannot_block_path" [drivers/firmware/efivars.ko] undefined!
>
> Caused by commit 1a1df768ea4e ("efi_pstore: Avoid deadlock in non-blocking paths").
>
> I have used the ia64 tree from next-20130110 for today.
> --
> Cheers,
> Stephen Rothwell sfr@...b.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists