From: Al Viro <viro@ZenIV.linux.org.uk>
To: Yang Shi <yang.s@alibaba-inc.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 4/8] vfs: remove unused hardirq.h
Date: Thu, 7 Dec 2017 19:21:56 +0000 [thread overview]
Message-ID: <20171207192156.GF21978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <0bfadf85-b499-5d2f-f0d2-20d229ba7fe2@alibaba-inc.com>
On Fri, Dec 08, 2017 at 03:12:52AM +0800, Yang Shi wrote:
> Hi folks,
>
> Any comment on this one?
Applied
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-07 19:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 23:02 [PATCH 1/8] mm: kmemleak: remove unused hardirq.h Yang Shi
2017-11-17 23:02 ` [PATCH 2/8] fs: pstore: " Yang Shi
2017-11-29 0:40 ` Kees Cook
2017-11-17 23:02 ` [PATCH 3/8] fs: btrfs: " Yang Shi
2017-11-20 13:25 ` David Sterba
2017-11-17 23:02 ` [PATCH 4/8] vfs: " Yang Shi
2017-12-07 19:12 ` Yang Shi
2017-12-07 19:21 ` Al Viro [this message]
2017-11-17 23:02 ` [PATCH 5/8] crypto: " Yang Shi
2017-11-20 16:29 ` Yang Shi
2017-11-29 6:38 ` [5/8] " Herbert Xu
2017-11-17 23:02 ` [PATCH 6/8] net: caif: " Yang Shi
2017-12-07 19:13 ` Yang Shi
2018-01-04 22:51 ` Yang Shi
2017-11-17 23:02 ` [PATCH 7/8] net: ovs: " Yang Shi
2017-11-18 1:48 ` Yang Shi
2017-12-07 19:14 ` Yang Shi
2017-12-07 19:27 ` [ovs-dev] " Pravin Shelar
2018-01-04 22:47 ` Yang Shi
2017-11-17 23:02 ` [PATCH 8/8] net: tipc: " Yang Shi
2017-12-07 19:15 ` Yang Shi
2017-12-07 19:20 ` Jon Maloy
2017-12-07 20:02 ` Yang Shi
2017-12-08 1:40 ` Ying Xue
2018-01-04 22:46 ` Yang Shi
2018-01-05 15:17 ` David Miller
2018-01-08 19:43 ` Yang Shi
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=20171207192156.GF21978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=yang.s@alibaba-inc.com \
/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).