linux-kernel - Re: [PATCH 12/49] MIPS: irq: Remove IRQF

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 Nov 2011 11:06:03 +0800
From:	Yong Zhang <yong.zhang0@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>, tglx@...utronix.de
Cc:	Ralf Baechle <ralf@...ux-mips.org>, linux-kernel@...r.kernel.org,
	linux-mips@...ux-mips.org
Subject: Re: [PATCH 12/49] MIPS: irq: Remove IRQF_DISABLED

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@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/