From: Ralf Baechle <ralf@linux-mips.org>
To: John Kacur <jkacur@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH cleanup] Re: + mips-vpe-remove-leftover-unlock_kernel.patch added to -mm tree
Date: Tue, 3 Nov 2009 23:15:41 +0100 [thread overview]
Message-ID: <20091103221541.GA25401@linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911032243530.6542@localhost.localdomain>
On Tue, Nov 03, 2009 at 10:52:41PM +0100, John Kacur wrote:
> > > I already have an equivalent patch in the MIPS kernel - Linus only needs
> > > to finally pull ...
> > >
> >
> > I didn't see such a patch in yesterday's linux-next..
I only have stuff to be pulled for 2.6.33 on my -next tree. Anything for
2.6.32 was in another tree.
> Linus picked-up Ralf's version of the patch for 2.6.32-rc6
> a22d621c80fb08f668ae3bfe62aeaae64b0b2b89
>
> That has the important part that removes the stray unlock_kernel, but
> unfortunately doesn't remove the smp_lock.h header.
>
> So, the last patch is just a clean-up. (no urgency).
>
> >From ae20d9169893112daaad1dc3af9f8559003a2bfb Mon Sep 17 00:00:00 2001
> From: John Kacur <jkacur@redhat.com>
> Date: Tue, 3 Nov 2009 22:15:55 +0100
> Subject: [PATCH] Remove BKL header.
>
> Now that the bkl has been removed, also remove the smp_lock.h include
In fact every single use of <linux/smp_lock.h> in arch/mips/ is unnecessary;
see patch for 2.6.33 in
http://www.linux-mips.org/git?p=upstream-sfr.git;a=commit;h=defde8dd822ddbab4ea1f8d2f5831e693bc75ad4
Ralf
next prev parent reply other threads:[~2009-11-03 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 7:01 + mips-vpe-remove-leftover-unlock_kernel.patch added to -mm tree akpm
[not found] ` <20091103140953.GA23611@linux-mips.org>
[not found] ` <20091103085613.373634ab.akpm@linux-foundation.org>
2009-11-03 21:52 ` [PATCH cleanup] " John Kacur
2009-11-03 22:15 ` Ralf Baechle [this message]
2009-11-03 22:24 ` John Kacur
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=20091103221541.GA25401@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.