[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090107205229.GB4597@elte.hu>
Date: Wed, 7 Jan 2009 21:52:29 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Mike Travis <travis@....com>
Cc: Ingo Molnar <mingo@...hat.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, Jack Steiner <steiner@....com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] cpumask: more cpumask updates
* Mike Travis <travis@....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@....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
--
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