From: David Sterba <dsterba@suse.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: clm@fb.com, stable@vger.kernel.org
Subject: Re: Btrfs patches for stable 4.8.x
Date: Wed, 4 Jan 2017 09:39:54 +0100 [thread overview]
Message-ID: <20170104083954.GW12081@suse.cz> (raw)
In-Reply-To: <20170103192204.GB10478@kroah.com>
On Tue, Jan 03, 2017 at 08:22:04PM +0100, Greg KH wrote:
> On Wed, Dec 14, 2016 at 10:49:53AM +0100, David Sterba wrote:
> > Hi,
> >
> > please apply the following patches to 4.8 series. There are fixes for user
> > reported problems with device deletion and hung umount, plus other stability
> > fixes. The commits apply cleanly to 4.8.14. Thanks.
> >
> > Commits:
> >
> > 9eb4a4a60b0e86a26f84cb5ac8f9493de6c3b1bb
>
> That commit is not in Linus's tree :(
>
> > 20411dafe87a8cc8bcea9fe6d8d2791606222520
>
> Neither is this one :(
>
> > 5f22e00270766e60be218a523acb1d9321abdafd
> > f8ddb1eca6815a77c5b4e0bc6f7eedd6a5cf52fd
> > bdce4057370d8e30b73ddef4721d97edb41c5390
> > 2be8911a7849a459f092b8acb9f428fb8c779a0c
> > eec7f79b72caad9cd1b051d18e02414653d50885
> > 0a28de62d44e8b9d1bd19fa84ef04e954da1b5d9
> > 9f7916b88b64ad2b8aef4758409dc6981de138cc
> > 029484589cbcc9c86d604b31603edf84fd90bf80
>
> I didn't check the rest of these as odds are, they are also wrong...
>
> Where did you get these git commit ids from?
Sorry, IDs got generated from the wrong list of patches, the correct
list for 4.8 is:
2571e739677f1e4c0c63f5ed49adcc0857923625
49303381f19ab16a371a061b67e783d3f570d56e
3561b9db70928f207be4570b48fc19898eeaef54
6bdf131fac2336adb1a628f992ba32384f653a55
cea67ab92d3d4da9f2b4141d87cb8664757daca0
a958eab0ed7fdc1b977bc25d3af6efedaa945488
0ccd05285e7f5a8e297e1d6dfc41e7c65757d6fa
4867268c57ff709a7b6b86ae6f6537d846d1443a
d5e84fd8d0634d056248b67463b42f6c85896a19
69ae5e4459e43e56f03d0987e865fbac2b05af2a
Applicable to 4.4:
2571e739677f1e4c0c63f5ed49adcc0857923625
49303381f19ab16a371a061b67e783d3f570d56e
3561b9db70928f207be4570b48fc19898eeaef54
6bdf131fac2336adb1a628f992ba32384f653a55
a958eab0ed7fdc1b977bc25d3af6efedaa945488
4867268c57ff709a7b6b86ae6f6537d846d1443a
69ae5e4459e43e56f03d0987e865fbac2b05af2a
Thanks.
next prev parent reply other threads:[~2017-01-04 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 9:49 Btrfs patches for stable 4.8.x David Sterba
2017-01-03 19:20 ` Greg KH
2017-01-03 19:22 ` Greg KH
2017-01-04 8:39 ` David Sterba [this message]
2017-01-04 9:38 ` 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=20170104083954.GW12081@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@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 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.