From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: ejt@redhat.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] dm btree: add ref counting ops for the leaves of top level" failed to apply to 4.1-stable tree
Date: Wed, 19 Aug 2015 09:42:55 -0700 [thread overview]
Message-ID: <20150819164255.GA19661@kroah.com> (raw)
In-Reply-To: <20150819163309.GA25908@redhat.com>
On Wed, Aug 19, 2015 at 12:33:09PM -0400, Mike Snitzer wrote:
> On Wed, Aug 19 2015 at 12:15pm -0400,
> gregkh@linuxfoundation.org <gregkh@linuxfoundation.org> wrote:
>
> >
> > The patch below does not apply to the 4.1-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> I think it'd be sufficient to just remove the remove_one() hunk from
> commit b0dc3c8bc1.
>
> Otherwise, commit b0dc3c8bc1 depends on these commits to apply cleanly:
> 4ec331c3ea
> aa0cd28d05
>
> But I'll have to reassess the applicability of commit b0dc3c8bc1 to
> earlier releases. I'll send a backport to stable@ if it is needed.
Please send any changes you want, I'm not going to hand-edit patches on
my own, sorry.
greg k-h
next prev parent reply other threads:[~2015-08-19 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 16:15 FAILED: patch "[PATCH] dm btree: add ref counting ops for the leaves of top level" failed to apply to 4.1-stable tree gregkh
2015-08-19 16:33 ` Mike Snitzer
2015-08-19 16:42 ` Greg KH [this message]
2015-08-19 18:45 ` [PATCH] dm btree: add ref counting ops for the leaves of top level btrees Mike Snitzer
2015-08-31 10:57 ` Luis Henriques
2015-08-31 10:57 ` Luis Henriques
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=20150819164255.GA19661@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ejt@redhat.com \
--cc=snitzer@redhat.com \
--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.