From: Alan Cox <alan@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH 00/11] BKL pruning and serial bug fixing
Date: Thu, 20 May 2010 19:06:05 +0100 [thread overview]
Message-ID: <20100520190605.141a70ad@linux.intel.com> (raw)
In-Reply-To: <20100520175636.GB17077@kroah.com>
On Thu, 20 May 2010 10:56:36 -0700
Greg KH <greg@kroah.com> wrote:
> On Wed, May 19, 2010 at 01:01:42PM +0100, Alan Cox wrote:
> > BKL elemination using the existing locks
>
> Hm, have all of these patches been in -next before now? Do you think
> these are ready to go into .35?
Sorry - you asked for them to be re-sent with the BKL removal fixes from
Arnd which is for .36. They aren't needed for .35 and don't really fix
anything that would be worth backporting either.
Not .35 material.
Alan
next prev parent reply other threads:[~2010-05-20 18:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 12:01 [PATCH 00/11] BKL pruning and serial bug fixing Alan Cox
2010-05-19 12:01 ` [PATCH 01/11] tty: Fix the digi acceleport driver NULL checks Alan Cox
2010-05-19 12:02 ` [PATCH 02/11] stallion: prune lock_kernel calls Alan Cox
2010-05-19 12:02 ` [PATCH 03/11] istallion: use bit ops for the board flags Alan Cox
2010-05-19 12:02 ` [PATCH 04/11] riscom8: kill use of lock_kernel Alan Cox
2010-05-19 12:02 ` [PATCH 05/11] isicom: kill off the BKL Alan Cox
2010-05-19 12:02 ` [PATCH 06/11] rocket: kill BKL Alan Cox
2010-05-19 12:02 ` [PATCH 07/11] synclink: kill the big kernel lock Alan Cox
2010-05-19 12:03 ` [PATCH 08/11] cyclades: Kill off BKL usage Alan Cox
2010-05-19 12:03 ` [PATCH 09/11] epca: Kill the big kernel lock Alan Cox
2010-05-19 12:03 ` [PATCH 10/11] specialix; Kill the BKL Alan Cox
2010-05-19 12:03 ` [PATCH 11/11] synclink: reworking locking a bit Alan Cox
2010-05-20 17:56 ` [PATCH 00/11] BKL pruning and serial bug fixing Greg KH
2010-05-20 18:06 ` Alan Cox [this message]
2010-05-20 19:01 ` Greg KH
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=20100520190605.141a70ad@linux.intel.com \
--to=alan@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).