From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Mike Travis <travis@sgi.com>,
Yinghai Lu <yinghai@kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: manual merge of the rr_cpumask tree
Date: Mon, 15 Dec 2008 17:11:34 +1030 [thread overview]
Message-ID: <200812151711.36134.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20081215170945.b91f3b9c.sfr@canb.auug.org.au>
On Monday 15 December 2008 16:39:45 Stephen Rothwell wrote:
> Hi Rusty,
>
> Today's linux-next merge of the rr_cpumask tree got a conflict in
> arch/x86/kernel/io_apic.c between commit
> 3145e941fcfe2548fa2270afb1a05bab3a6bc418 ("x86, MSI: pass irq_cfg and
> irq_desc") from the sparseirq tree and commit
> 0de26520c7cabf36e1de090ea8092f011a6106ce ("cpumask: make irq_set_affinity
> () take a const struct cpumask") from the rr_cpumask tree.
>
> There are lots of overlapping changes. I fixed it up (see below) and can carry the
> fix as necessary.
I have performed this merge before. The results are in
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-ingo.git
Ingo, can you pull these into cpus4096? It's just the cpumask/cpus4096 merge.
Thanks,
Rusty.
next prev parent reply other threads:[~2008-12-15 6:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 6:09 linux-next: manual merge of the rr_cpumask tree Stephen Rothwell
2008-12-15 6:41 ` Rusty Russell [this message]
2008-12-15 16:27 ` Mike Travis
2008-12-15 18:40 ` Mike Travis
2008-12-16 5:40 ` Rusty Russell
2008-12-16 6:02 ` Mike Travis
2008-12-16 6:09 ` Stephen Rothwell
2008-12-16 16:03 ` Mike Travis
2008-12-16 20:55 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-12-15 6:09 Stephen Rothwell
2009-01-02 2:35 Stephen Rothwell
2009-01-02 5:47 ` Rusty Russell
2009-01-02 6:21 ` Stephen Rothwell
2009-01-02 17:21 ` Mike Travis
2009-01-02 9:59 ` Ingo Molnar
2009-01-02 12:52 ` Ingo Molnar
2009-01-02 2:43 Stephen Rothwell
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=200812151711.36134.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=travis@sgi.com \
--cc=yinghai@kernel.org \
/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).