From: Sedat Dilek <sedat.dilek@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: lsf@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all
Date: Sat, 29 Mar 2014 11:04:51 +0100 [thread overview]
Message-ID: <CA+icZUUqDVROfgcpULciNaP=h_EJkBJHGCLNHFaNHjEEeVqV5A@mail.gmail.com> (raw)
In-Reply-To: <20140328161806.GA31772@thunk.org>
On Fri, Mar 28, 2014 at 5:18 PM, <tytso@mit.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@gmail.com>
>
> Thanks, applied.
>
...and pushed?
> In the future, it would be great at least cc patches to
> linux-ext4@vger.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@vger.kernel.org, while xfstests patches
> and discussion happen on xfs@oss.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 -
next prev parent reply other threads:[~2014-03-29 10:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 9:03 [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all Sedat Dilek
2014-03-28 16:18 ` tytso
2014-03-29 10:04 ` Sedat Dilek [this message]
2014-03-29 14:04 ` Theodore Ts'o
2014-03-31 2:51 ` [Lsf] " Dave Chinner
2014-04-01 2:37 ` Theodore Ts'o
2014-04-01 22:28 ` Dave Chinner
2014-04-02 14:26 ` Theodore Ts'o
2014-04-03 1:14 ` Dave Chinner
2014-04-03 10:26 ` Lukáš Czerner
2014-04-03 17:05 ` Andy Lutomirski
2014-04-03 17:35 ` Theodore Ts'o
2014-04-03 17:42 ` Andy Lutomirski
2014-04-03 19:06 ` Eric Sandeen
2014-04-03 19:21 ` Andy Lutomirski
2014-04-03 21:46 ` Eric Sandeen
2014-04-03 19:30 ` Theodore Ts'o
2014-04-03 21:20 ` Dave Chinner
2014-04-03 13:16 ` Mel Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+icZUUqDVROfgcpULciNaP=h_EJkBJHGCLNHFaNHjEEeVqV5A@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf@lists.linux-foundation.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).