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, 29 Mar 2014 11:04:51 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	lsf@...ts.linux-foundation.org,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all

On Fri, Mar 28, 2014 at 5:18 PM,  <tytso@....edu> wrote:
> On Fri, Mar 28, 2014 at 10:03:19AM +0100, Sedat Dilek wrote:
>> Use 'getconf _NPROCESSORS_ONLN' to determine the total number
>> of available ("online") CPUs.
>>
>> I have seen this 1st in some build-scripts of Grml project and
>> had some discussions with Thorsten Glaser on this topic.
>>
>> Signed-off-by: Sedat Dilek <sedat.dilek@...il.com>
>
> Thanks, applied.
>

...and pushed?

> In the future, it would be great at least cc patches to
> linux-ext4@...r.kernel.org, since I rely on patchwork to make sure
> patches don't end up falling through the cracks.
>
> If we start getting a huge number of patches to xfstests-bld, and
> people start getting confused/annoyed about how xfstests-bld issues
> get discussed on linux-ext4@...r.kernel.org, while xfstests patches
> and discussion happen on xfs@....sgi.com, we could consider creating a
> new mailing list --- especially given that based on a challenge which
> Greg K-H gave us at the kernel pannel at Collab Summit, we'll at least
> be looking at cleaning up and then trying to get into the linux kernel
> mainline sources some combination of xfstests plus some infrastructure
> automation (perhaps strongly based on what I've been working here in
> the xfstests-bld tree) to run xfstests.
>

Please, document the handling of patches (and where someone can get informed).

- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ