From: Greg KH <greg@kroah.com>
To: Harsh Shandilya <harsh@prjkt.io>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 3.18.y 0/5] Backports for 3.18.y
Date: Tue, 24 Apr 2018 14:30:05 +0200 [thread overview]
Message-ID: <20180424123005.GC28044@kroah.com> (raw)
In-Reply-To: <20180422200746.29118-1-harsh@prjkt.io>
On Mon, Apr 23, 2018 at 01:37:41AM +0530, Harsh Shandilya wrote:
> A few more patches that were Cc'd stable but failed to apply
> to 3.18, backported with the 4.4 queue variants as reference
> wherever required.
I've applied the ext4 patches, I'll wait for you to redo the other two.
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-24 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 20:07 [PATCH 3.18.y 0/5] Backports for 3.18.y Harsh Shandilya
2018-04-22 20:07 ` [PATCH 3.18.y 1/5] ext4: fix deadlock between inline_data and ext4_expand_extra_isize_ea() Harsh Shandilya
2018-04-22 20:07 ` [PATCH 3.18.y 2/5] ext4: bugfix for mmaped pages in mpage_release_unused_pages() Harsh Shandilya
2018-04-22 20:07 ` [PATCH 3.18.y 3/5] mm: allow GFP_{FS,IO} for page_cache_read page cache allocation Harsh Shandilya
2018-04-22 22:46 ` Michal Hocko
2018-04-23 3:16 ` Harsh Shandilya
2018-04-22 20:07 ` [PATCH 3.18.y 4/5] mm/filemap.c: fix NULL pointer in page_cache_tree_insert() Harsh Shandilya
2018-04-22 20:07 ` [PATCH 3.18.y 5/5] ext4: don't update checksum of new initialized bitmaps Harsh Shandilya
2018-04-24 12:30 ` Greg KH [this message]
2018-04-24 12:59 ` [PATCH 3.18.y 0/5] Backports for 3.18.y Harsh Shandilya
2018-04-24 13:11 ` Harsh Shandilya
2018-04-24 14:03 ` Greg KH
2018-04-24 14:11 ` Harsh Shandilya
2018-04-24 14:24 ` 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=20180424123005.GC28044@kroah.com \
--to=greg@kroah.com \
--cc=harsh@prjkt.io \
--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 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).