From: Josh Hunt <johunt@akamai.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-ext4@vger.kernel.org,
tytso@mit.edu, jack@suse.cz
Subject: Re: [PATCH] ext4: fix warning in ext4_da_update_reserve_space()
Date: Tue, 03 Feb 2015 16:57:22 -0600 [thread overview]
Message-ID: <54D15252.5000805@akamai.com> (raw)
In-Reply-To: <20150203225343.GA3539@kroah.com>
On 02/03/2015 04:53 PM, Greg KH wrote:
> On Thu, Jan 08, 2015 at 03:48:28PM -0500, Josh Hunt wrote:
>> Please add the patch below and referenced dependency (0e95c22) to stable
>> 3.10.y.
>
> There is no such commit "0e95c22" in Linus's tree, do you mean
> "1c8924eb106c1ac755d5d35ce9b3ff42e89e2511"? If so, that doesn't apply
> to 3.10 at all, so I can't apply that on, and so, can't apply the patch
> below either :(
>
> Care to provide proper backports of both of them?
>
> thanks,
>
> greg k-h
>
Hey Greg
I thought we discussed this already. You've already applied these
patches to 3.10.y:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.10.y&id=23d5efc071f5f47257e5b33c41534a30b1099cc3
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.10.y&id=4e9eb2afbc494a56e35bf6c1a621f579eb1199b2
I messed up the commit id reference in my original submission to you,
but sent a followup. Given that both patches are in 3.10.y now I don't
think there's anything else to do.
Let me know if you need something else from me.
Thanks
Josh
next prev parent reply other threads:[~2015-02-03 22:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 20:48 [PATCH] ext4: fix warning in ext4_da_update_reserve_space() Josh Hunt
2015-01-22 3:31 ` Josh Hunt
2015-01-28 0:12 ` Greg KH
2015-01-28 0:14 ` Josh Hunt
2015-02-03 22:53 ` Greg KH
2015-02-03 22:57 ` Josh Hunt [this message]
2015-02-03 23:13 ` Greg KH
2015-02-03 23:15 ` Josh Hunt
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=54D15252.5000805@akamai.com \
--to=johunt@akamai.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--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 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).