linux-kernel - Re: linux-next: build failure after merge of the block tree

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: <AANLkTimpfhc+CpxBW1xtHxuU7jN3ix_fh36jjXTxDnxM@mail.gmail.com>
Date:	Fri, 7 Jan 2011 19:20:16 +0100
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the block tree

On Fri, Jan 7, 2011 at 7:04 PM, Sedat Dilek <sedat.dilek@...glemail.com> wrote:
> On Fri, Jan 7, 2011 at 4:08 PM, Jens Axboe <axboe@...nel.dk> wrote:
>> On 2011-01-07 15:22, Stephen Rothwell wrote:
>>> Hi,
>>>
>>> On Fri, 7 Jan 2011 14:19:33 +0100 Sedat Dilek <sedat.dilek@...glemail.com> wrote:
>>>>
>>>> Hmm, I have pulled-in freshly from linux-2.6-block#for-next after you
>>>> published latest linux-next (next-20110107).
>>>> So, I guessed the (reported) issue is fixed, now.
>>>
>>> No, the commit that caused the warnings was removed when I went back to
>>> using the block tree from next-20110106.  So it will come back unless
>>> fixed.
>>
>> It is fixed in linux-2.6-block#for-next as-of earlier today, so if Sedat
>> pulled from there it should be gone.
>>
>> --
>> Jens Axboe
>>
>>
>
> I guess 0002 should fix it, its not the case (patch + "big diff" attached).
>
> - Sedat -
>
[...]

Missing "blktrace: add missing probe argument to block_bio_complete" patch.

- Sedat -
--
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/