From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Hellstrom <daniel@gaisler.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: manual merge of the tip tree with the sparc tree
Date: Fri, 20 May 2011 12:18:02 +1000 [thread overview]
Message-ID: <20110520121802.f0bf0fea.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4DD51D37.3010907@gaisler.com>
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
Hi Daniel,
On Thu, 19 May 2011 15:37:59 +0200 Daniel Hellstrom <daniel@gaisler.com> wrote:
>
> I looked at linux-next and I think the call to the scheduler_ipi is
> missing in the resched interrupt routine. I believe that the below patch
> should be applied ontop of linux-next. Could you include it in the merge
> or what do you suggest I do?
That patch (if correct) needs to be applied to some tree, linux-next just
takes what it is given. That patch is really beyond a merge fix as that
code exists on neither tree.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-05-20 2:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 3:14 linux-next: manual merge of the tip tree with the sparc tree Stephen Rothwell
2011-05-19 13:37 ` Daniel Hellstrom
2011-05-19 15:35 ` Peter Zijlstra
2011-05-20 6:07 ` Daniel Hellstrom
2011-05-20 8:11 ` Peter Zijlstra
2011-05-20 12:48 ` Daniel Hellstrom
2011-05-20 13:24 ` Peter Zijlstra
2011-05-20 2:18 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-28 6:38 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=20110520121802.f0bf0fea.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=daniel@gaisler.com \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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