From: Chris Mason <chris.mason@oracle.com>
To: Brad Figg <brad.figg@canonical.com>
Cc: "Yan, Zheng " <yanzheng@21cn.com>, linux-btrfs@vger.kernel.org
Subject: Re: Regression in 2.6.35 RC1 (Ubuntu 2.6.35-1-generic)
Date: Fri, 11 Jun 2010 15:40:49 -0400 [thread overview]
Message-ID: <20100611194049.GB3018@think> (raw)
In-Reply-To: <4C125D8A.40408@canonical.com>
On Fri, Jun 11, 2010 at 09:00:10AM -0700, Brad Figg wrote:
> On 06/10/2010 11:33 PM, Yan, Zheng wrote:
> >>
> >
> >I have already sent a patch for this.
> >http://www.spinics.net/lists/linux-btrfs/msg05150.html
> >
> >Yan, Zheng
> >--
> >To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> I've not seen this patch hit lkml yet.
This is now in the master branch of the btrfs-unstable tree.
-chris
prev parent reply other threads:[~2010-06-11 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 4:54 Regression in 2.6.35 RC1 (Ubuntu 2.6.35-1-generic) Brad Figg
2010-06-11 6:33 ` Yan, Zheng
2010-06-11 16:00 ` Brad Figg
2010-06-11 19:40 ` Chris Mason [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=20100611194049.GB3018@think \
--to=chris.mason@oracle.com \
--cc=brad.figg@canonical.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yanzheng@21cn.com \
/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).