Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: John Crispin <john@phrozen.org>
To: linux-mips@linux-mips.org
Subject: Re: [MIPS] Pull request for 3.8
Date: Sun, 11 Nov 2012 19:25:10 +0100	[thread overview]
Message-ID: <509FED86.8020104@phrozen.org> (raw)
In-Reply-To: <CAJiQ=7DKn9hUr_Y2xn6r7ZRNQ3FTOXe+rMq=ZigxMMZdL-d0TA@mail.gmail.com>

On 11/11/12 19:19, Kevin Cernekee wrote:
> On Sun, Nov 11, 2012 at 10:03 AM, John Crispin<blogic@openwrt.org>  wrote:
>> Hi Ralf,
>>
>> here is my queue of patches i consider ready for 3.8.
> [snip]
>> Kevin Cernekee (1):
>>        MIPS: tlbex: Fix section mismatches
>
> The section mismatch in question first showed up in 3.7-rc2 with
> commit 02a5417751, so it's a recent regression with an easy fix.
>
> What do you think about rolling the fix into 3.7 instead of 3.8?


ralf,

can you send this to linus for 3.7-rc5 ? i would remove it from my tree 
if you do.

	John

      reply	other threads:[~2012-11-11 18:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 18:03 [MIPS] Pull request for 3.8 John Crispin
2012-11-11 18:19 ` Kevin Cernekee
2012-11-11 18:25   ` John Crispin [this message]

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=509FED86.8020104@phrozen.org \
    --to=john@phrozen.org \
    --cc=linux-mips@linux-mips.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