public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Clemens Schwaighofer <cs@tequila.co.jp>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11-ac1
Date: Mon, 7 Mar 2005 22:49:26 -0800	[thread overview]
Message-ID: <20050308064926.GV28536@shell0.pdx.osdl.net> (raw)
In-Reply-To: <B0B9168A9B666B9CF980CB7C@[192.168.12.2]>

* Clemens Schwaighofer (cs@tequila.co.jp) wrote:
> --On Monday, March 07, 2005 09:34:22 PM +0000 Alan Cox 
> <alan@lxorguk.ukuu.org.uk> wrote:
> 
> >For a couple of reasons I've not yet merged Greg's 2.6.11.1 yet but this
> >diff should actually apply to either right now.
> >
> >2.6.11-ac1
> >o	Fix jbd race in ext3				(Stephen Tweedie)
> 
> will that patch actually appear in 2.6.11.2? At least it looks like a 
> candidate for me ...

Yes, we are intending to pick up bits from -ac (you might have missed
that in another thread).

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2005-03-08  6:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 21:34 Linux 2.6.11-ac1 Alan Cox
2005-03-08  6:02 ` Clemens Schwaighofer
2005-03-08  6:49   ` Chris Wright [this message]
2005-03-08  6:52     ` Clemens Schwaighofer
2005-03-08 12:47     ` Stephen C. Tweedie
2005-03-08 12:00 ` Andre Tomt
2005-03-09  7:26 ` CaT
2005-03-09 15:51   ` Alan Cox
2005-03-10  8:03     ` Denis Vlasenko
2005-03-09 16:26   ` Bartlomiej Zolnierkiewicz
2005-03-09 16:38     ` Alan Cox
2005-03-09 16:43       ` Bartlomiej Zolnierkiewicz
2005-03-09 22:22         ` CaT
2005-03-09 22:39           ` Alan Cox
2005-03-10  9:06             ` Tupshin Harper
2005-03-10 15:01               ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-03-07 23:26 Indrek Kruusa

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=20050308064926.GV28536@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cs@tequila.co.jp \
    --cc=linux-kernel@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