linux-kernel - RE: linux-next: Tree for June 3 (staging)

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 6 Jun 2009 16:37:44 +0800
From:	"Gao, Yunpeng" <yunpeng.gao@...el.com>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
CC:	Greg KH <greg@...ah.com>, Greg KH <gregkh@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: linux-next: Tree for June 3 (staging)



>-----Original Message-----
>From: Bartlomiej Zolnierkiewicz [mailto:bzolnier@...il.com]
>Sent: 2009年6月6日 2:58
>To: Gao, Yunpeng
>Cc: Greg KH; Greg KH; linux-kernel@...r.kernel.org
>Subject: Re: linux-next: Tree for June 3 (staging)
>
>On Friday 05 June 2009 05:31:21 Gao, Yunpeng wrote:
>> Hi Greg,
>>
>> Thanks for your quick response.
>>
>> The root cause of the build-errors in ffsport.c is that the kernel block layer
>APIs are different in linux-next tree (.../linux/kernel/git/sfr/linux-next.git)
>than in Linus' kernel tree (.../linux/kernel/git/torvalds/linux-2.6.git).
>>
>> Yesterday, after modify code in ffsport.c to sync up with the block layer APIs
>changes, I have make the kernel against linux-next tree and found no build error
>/ warnings.
>>
>> Then I generated the patch again Linus' kernel tree, tag 'v2.6.30-rc8' and
>sent the patch to you. This patch uses the new block layer APIs and is target
>for the linux-next tree.
>>
>> I guess the below build errors are caused by compiling the patch code in Linus'
>kernel tree. As the block layer API's in Linus' kernel tree is still the old
>one, it'll report this kind of 'implicit declaration of function ...' error.
>I'm sorry for the mis-communication.
>>
>> Now, I'm a bit confused with the process :-) Which git tree should I select
>to generate patch against and submit to? The linux-next tree or Linus' kerner
>tree?
>
>One solution would be to generate the _main_ patch against Linus' tree
>(for Greg to include in staging tree) and then generate _incremental_
>patch with changes to account for block layer API update (for Stephen
>to include in linux-next)..
>
>Thanks.
>Bart

Hi Bart,
Thanks a lot for the good idea. I'll generate the two patches and send them to Greg then.

Thanks.

Rgds,
Yunpeng