linux-kernel - Re: [RFC/PULL 00/11] introduce export.h; reduce module.h usage

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]

Message-ID: <4E43D4AD.6080702@windriver.com>
Date:	Thu, 11 Aug 2011 09:10:05 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Mike Frysinger <vapier.adi@...il.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>, <mingo@...e.hu>,
	<linux-kernel@...r.kernel.org>, <akpm@...ux-foundation.org>,
	<linux-arch@...r.kernel.org>, <sfr@...b.auug.org.au>
Subject: Re: [RFC/PULL 00/11] introduce export.h; reduce module.h usage

On 11-08-11 12:34 AM, Mike Frysinger wrote:
> On Wed, Aug 10, 2011 at 15:09, Paul Gortmaker wrote:
>> On 11-08-07 10:42 PM, Mike Frysinger wrote:
>>
>> [...]
>>
>>> Blackfin is broken because of this.  a simple grep of the tree
>>
>> I've run all the in-tree blackfin configs, so it is all good.
> 
> so you made a change and it's all good <now> ?

Correct.

> 
>> Have you thought about getting at least one blackfin defconfig in
>> the linux-next build coverage?  Gives you a better chance of
>> having people see when they've broken it.
> 
> all of the blackfin defconfigs get tested nightly in linux-next by an
> ADI build machine.  i just didnt have a chance to review the logs as i
> was traveling.

That is good, but as you've noted, it isn't something that anyone
else can see when they are combing the normal linux-next build
results below looking to see if they broke anything.

http://kisskb.ellerman.id.au/kisskb/branch/9/

Thanks,
Paul.

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