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: <CAMjpGUch3O_DWKv39A_H91bU5ypSxSgHjSVX8WYDnGxKVBPZLQ@mail.gmail.com>
Date:	Thu, 11 Aug 2011 13:15:17 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.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 Thu, Aug 11, 2011 at 09:10, Paul Gortmaker wrote:
> On 11-08-11 12:34 AM, Mike Frysinger wrote:
>> On Wed, Aug 10, 2011 at 15:09, Paul Gortmaker wrote:
>>> 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/

ive never heard of this site before, and there doesnt appear to be any
documentation on that site about it
-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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ