From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Jack Steiner <steiner@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] cpumask: more cpumask updates
Date: Wed, 7 Jan 2009 21:52:29 +0100 [thread overview]
Message-ID: <20090107205229.GB4597@elte.hu> (raw)
In-Reply-To: <20090107195832.265117000@polaris-admin.engr.sgi.com>
* Mike Travis <travis@sgi.com> wrote:
>
> One big change to irq_desc and a few smaller maintenance type updates.
>
> cpumask: update irq_desc to use cpumask_var_t
> cpumask: Use topology_core_cpumask()/topology_thread_cpumask()
> cpumask: convert misc driver functions
> cpumask: convert drivers/net/sfc
> cpumask: convert other misc kernel functions
>
> Based on tip/cpus4096: v2.6.28-5703-g1d1a70e
>
> (Ingo - I added a blank line before the From: part and that seems to
> separate it from the Subject. Hopefully your git-am will still
> recognizes it - I did try a git-am here and it seemed to work ok.)
>
> Signed-off-by: Mike Travis <travis@sgi.com>
Since you have it in a Git tree, why dont you send me a pull request?
I might be more picky about pull requests in general (because it's harder
to fix up a pulled tree than to fix up commits that come from emails - and
it's also more work for you if i refuse to pull than if i have some
comments over email-patches), but it's a much better (more scalable)
workflow in the long run than the email path.
Ingo
next prev parent reply other threads:[~2009-01-07 20:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 19:58 [PATCH 0/5] cpumask: more cpumask updates Mike Travis
2009-01-07 19:58 ` [PATCH 1/5] cpumask: update irq_desc to use cpumask_var_t Mike Travis
2009-01-07 20:27 ` Yinghai Lu
2009-01-07 20:27 ` Yinghai Lu
2009-01-07 22:32 ` Mike Travis
2009-01-07 22:32 ` Mike Travis
2009-01-08 3:15 ` Yinghai Lu
2009-01-08 3:15 ` Yinghai Lu
2009-01-08 15:45 ` Mike Travis
2009-01-08 19:31 ` Yinghai Lu
2009-01-08 18:40 ` [PATCH 1/5] cpumask: update irq_desc to use cpumask_var_t: fix Mike Travis
2009-01-07 19:58 ` [PATCH 2/5] cpumask: Use topology_core_cpumask()/topology_thread_cpumask() Mike Travis
2009-01-19 17:11 ` Ben Hutchings
2009-01-07 19:58 ` [PATCH 3/5] cpumask: convert misc driver functions Mike Travis
2009-01-10 10:57 ` Rusty Russell
2009-01-16 18:42 ` Tony Luck
2009-01-16 18:55 ` Mike Travis
2009-01-16 22:02 ` Mike Travis
2009-01-22 13:11 ` Robert Richter
2009-01-22 13:14 ` [PATCH] cpumask: modifiy oprofile initialization Robert Richter
2009-01-22 13:37 ` Ingo Molnar
2009-01-22 17:20 ` Mike Travis
2009-01-22 17:40 ` Ingo Molnar
2009-01-22 19:41 ` Mike Travis
2009-01-22 16:56 ` Mike Travis
2009-01-23 14:12 ` Robert Richter
2009-01-07 19:58 ` [PATCH 4/5] cpumask: convert drivers/net/sfc Mike Travis
2009-01-19 17:08 ` Ben Hutchings
[not found] ` <200901201209.34854.rusty@rustcorp.com.au>
2009-01-20 18:26 ` [PATCH 4/5] cpumask: convert drivers/net/sfc [PATCH supplied] Mike Travis
2009-01-26 15:04 ` [PATCH] sfc: modify allocation error message Mike Travis
2009-01-27 12:13 ` Ben Hutchings
2009-01-07 19:58 ` [PATCH 5/5] cpumask: convert other misc kernel functions Mike Travis
2009-01-07 20:52 ` Ingo Molnar [this message]
2009-01-07 21:20 ` [PATCH 0/5] cpumask: more cpumask updates Mike Travis
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=20090107205229.GB4597@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.