[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130826221957.GA2782@kroah.com>
Date: Mon, 26 Aug 2013 15:19:57 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Kent Overstreet <kmo@...erainc.com>
Cc: stable@...r.kernel.org, linux-bcache@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Bcache fixes for stable
On Mon, Aug 26, 2013 at 03:02:49PM -0700, Kent Overstreet wrote:
> Two fixes that went into 3.11 should've been marked for stable, but I
> screwed up and forgot to mark them.
>
> One of them fixes bugs that appear to being hit in the wild, so please
> pull these:
>
> The following changes since commit 0a4b6d4ff200a553951f77f765971cb3e4c91ec0:
>
> Linux 3.10.9 (2013-08-20 15:40:47 -0700)
>
> are available in the git repository at:
>
> git://evilpiepirate.org/~kent/linux-bcache.git bcache-for-3.10
>
> for you to fetch changes up to a213846fafcdf52153dfebf8b1671498a72b6285:
>
> bcache: FUA fixes (2013-08-26 14:56:52 -0700)
>
> ----------------------------------------------------------------
> Kent Overstreet (1):
> bcache: FUA fixes
>
> Kumar Amit Mehta (1):
> md: bcache: io.c: fix a potential NULL pointer dereference
Can I get a hint as to what the git commit ids of these patches are in
Linus's tree?
Ideally, that's all you need to send me, but if you want to send me a
git pull, that's fine too, but please use a signed tag, otherwise it's
just a random tree...
Also, if you do a git pull, I need the git commit ids in the changelog
entry that match Linus's tree, so people (like me) can verify things.
For now, I can edit these two patches and add them in, if you give me
the git commit ids to verify them.
thanks,
greg k-h
--
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/
Powered by blists - more mailing lists