linux-kernel - Re: linux-next: Tree for September 16 (do

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTikNpvwuBe9LvDiC3+0=q57N0c=dyf+N=VMv_nYu@mail.gmail.com>
Date:	Fri, 17 Sep 2010 22:17:47 -0500
From:	Will Drewry <wad@...omium.org>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Randy Dunlap <randy.dunlap@...cle.com>
Subject: Re: linux-next: Tree for September 16 (do_mounts.c)

On Fri, Sep 17, 2010 at 3:00 AM, Jens Axboe <axboe@...nel.dk> wrote:
> On 2010-09-16 23:31, Stephen Rothwell wrote:
>> On Thu, 16 Sep 2010 09:11:25 -0700 Randy Dunlap <randy.dunlap@...cle.com> wrote:
>>>
>>> When CONFIG_BLOCK is not enabled:
>>>
>>> init/do_mounts.c:71: error: implicit declaration of function 'dev_to_part'
>>> init/do_mounts.c:71: warning: initialization makes pointer from integer without a cast
>>> init/do_mounts.c:73: error: dereferencing pointer to incomplete type
>>> init/do_mounts.c:76: error: dereferencing pointer to incomplete type
>>> init/do_mounts.c:76: error: dereferencing pointer to incomplete type
>>> init/do_mounts.c:102: error: implicit declaration of function 'part_pack_uuid'
>>> init/do_mounts.c:104: error: 'block_class' undeclared (first use in this function)
>>
>> Caused by commit b5af921ec02333e943efb59aca4f56b78fc0e100 ("init: add
>> support for root devices specified by partition UUID") from the block tree.
>
> Thanks for the report Randy, I've merged a fix for this.

Thanks and sorry!
will
--
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/