From: Felipe Balbi <balbi@ti.com>
To: "Theodore Ts'o" <tytso@mit.edu>, Felipe Balbi <balbi@ti.com>,
Christoph Hellwig <hch@lst.de>, <linux-ext4@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>, <stable@vger.kernel.org>,
Nishanth Menon <nm@ti.com>
Subject: Re: Please revert 08439fec266c3cc5702953b4f54bdf5649357de0
Date: Tue, 18 Aug 2015 10:19:19 -0500 [thread overview]
Message-ID: <20150818151919.GE9143@saruman.tx.rr.com> (raw)
In-Reply-To: <20150818005437.GA7535@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Mon, Aug 17, 2015 at 08:54:37PM -0400, Theodore Ts'o wrote:
> On Mon, Aug 17, 2015 at 02:45:03PM -0500, Felipe Balbi wrote:
> > Hi Theodore,
> >
> > as you already know, commit 08439fec266c (ext4: remove
> > block_device_ejected) caused a regression for (at least) USB attached
> > storage devices.
> >
> > You provided a fix for the regression by reverting that commit in
> > b9e43f49f672 (Revert "ext4: remove block_device_ejected"). This
> > revert is, currently, on linux-next but broken commit is part of
> > v4.1-final and, thus, part of v4.1 LTS.
> >
> > Could you please mark your revert for v4.1+ stable ? If it's not too
> > late to get it in v4.2-final, that would be great, otherwise we a Cc
> > stable would suffice anyway.
> >
> > In summary, commit 08439fec266c needs to be reverted on both v4.1-stable
> > and v4.2.
>
> Already done. See the latest version of the dev branch. I noticed
> this morning that I needed to mark it for stable, and took care of it.
cool, thanks
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-08-18 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 19:45 Please revert 08439fec266c3cc5702953b4f54bdf5649357de0 Felipe Balbi
2015-08-18 0:54 ` Theodore Ts'o
2015-08-18 15:19 ` Felipe Balbi [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=20150818151919.GE9143@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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.