Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Yong Zhang <yong.zhang0@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, tglx@linutronix.de
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 12/49] MIPS: irq: Remove IRQF_DISABLED
Date: Mon, 7 Nov 2011 11:06:03 +0800	[thread overview]
Message-ID: <20111107030603.GA3893@zhy> (raw)
In-Reply-To: <20111107134912.0878664493f1110ceefb98a6@canb.auug.org.au>

On Mon, Nov 07, 2011 at 01:49:12PM +1100, Stephen Rothwell wrote:
> Hi Yong,
> 
> On Mon, 7 Nov 2011 10:10:48 +0800 Yong Zhang <yong.zhang0@gmail.com> wrote:
> >
> > On Fri, Nov 04, 2011 at 12:21:06PM +0000, Ralf Baechle wrote:
> > > Thanks, queued for 3.3.  I resolved a conflict in dbdma.c and remove
> > > one IRQF_DISABLED which had been missed in arch/mips/kernel/perf_event.c.
> > 
> > And FYI, my patch is based on next-20111014 when I made it.
> 
> You should never base anything on top of a linux-next tree.  You should
> use the tree you are fixing (Linus' or the Mips tree or ...) as the base.

Thanks for your reminding Stephen :)

So I guess 'basing on linux-next' also brings some trouble to tglx,
which is hard for him to pick them up.

I think I should base my patch on -tip for the leftovers, tglx?
Or let me know your opinion if you have different idea.

Thanks,
Yong

      reply	other threads:[~2011-11-07  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1319277421-9203-1-git-send-email-yong.zhang0@gmail.com>
2011-10-22  9:56 ` [PATCH 12/49] MIPS: irq: Remove IRQF_DISABLED Yong Zhang
2011-11-04 12:21   ` Ralf Baechle
2011-11-07  2:10     ` Yong Zhang
2011-11-07  2:49       ` Stephen Rothwell
2011-11-07  3:06         ` Yong Zhang [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=20111107030603.GA3893@zhy \
    --to=yong.zhang0@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=sfr@canb.auug.org.au \
    --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