All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Can not compile Ecovec board
Date: Fri, 26 Aug 2011 08:14:16 +0000	[thread overview]
Message-ID: <20110826081415.GA13697@linux-sh.org> (raw)
In-Reply-To: <87aaaxou97.wl%kuninori.morimoto.gx@renesas.com>

On Fri, Aug 26, 2011 at 03:18:26PM +0900, Nobuhiro Iwamatsu wrote:
> 2011/8/26 Nobuhiro Iwamatsu <iwamatsu@nigauri.org>:
> > 2011/8/26 Magnus Damm <magnus.damm@gmail.com>:
> >> On Fri, Aug 26, 2011 at 1:30 PM, Nobuhiro Iwamatsu <iwamatsu@nigauri.org> wrote:
> >>> This was already revised in linux-next tree.
> >>
> >> That's great, but shouldn't build fixes be solved for the RC kernels
> >> if possible?
> >>
> >> People really need to learn how to separate build fixes from new
> >> development, otherwise everything will turn to shit.
> >>
> >
> > The commitment to revise this problem seems to be taken in with
> > signed-off of Paul by repository of Paul.
> > I think that It will be up to Paul whether this is taken-in in rc3.
> > Paul, do you think about this?
> >
> Sorry, commit is not in Paul's repository.
> This is in Paul Gortmaker's tree.
> 
I've had the same fix in my tree for some time, so I'm not sure what
you're looking at. It'll be included with the next batch of updates for
the next -rc, as usual.

      parent reply	other threads:[~2011-08-26  8:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26  1:07 Can not compile Ecovec board Kuninori Morimoto
2011-08-26  4:30 ` Nobuhiro Iwamatsu
2011-08-26  4:51 ` Magnus Damm
2011-08-26  5:12 ` Kuninori Morimoto
2011-08-26  5:24 ` Kuninori Morimoto
2011-08-26  6:05 ` Nobuhiro Iwamatsu
2011-08-26  6:18 ` Nobuhiro Iwamatsu
2011-08-26  8:14 ` Paul Mundt [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=20110826081415.GA13697@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.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 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.