linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ying Xue <ying.xue@windriver.com>
To: Yang Shi <yang.s@alibaba-inc.com>, <linux-kernel@vger.kernel.org>
Cc: <linux-mm@kvack.org>, <linux-fsdevel@vger.kernel.org>,
	<linux-crypto@vger.kernel.org>, <netdev@vger.kernel.org>,
	Jon Maloy <jon.maloy@ericsson.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 8/8] net: tipc: remove unused hardirq.h
Date: Fri, 8 Dec 2017 09:40:30 +0800	[thread overview]
Message-ID: <4ed1efbc-5fb8-7412-4f46-1e3a91a98373@windriver.com> (raw)
In-Reply-To: <1510959741-31109-8-git-send-email-yang.s@alibaba-inc.com>

On 11/18/2017 07:02 AM, Yang Shi wrote:
> Preempt counter APIs have been split out, currently, hardirq.h just
> includes irq_enter/exit APIs which are not used by TIPC at all.
> 
> So, remove the unused hardirq.h.
> 
> Signed-off-by: Yang Shi <yang.s@alibaba-inc.com>
> Cc: Jon Maloy <jon.maloy@ericsson.com>
> Cc: Ying Xue <ying.xue@windriver.com>
> Cc: "David S. Miller" <davem@davemloft.net>

Tested-by: Ying Xue <ying.xue@windriver.com>
Acked-by: Ying Xue <ying.xue@windriver.com>

> ---
>  net/tipc/core.h | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/net/tipc/core.h b/net/tipc/core.h
> index 5cc5398..099e072 100644
> --- a/net/tipc/core.h
> +++ b/net/tipc/core.h
> @@ -49,7 +49,6 @@
>  #include <linux/uaccess.h>
>  #include <linux/interrupt.h>
>  #include <linux/atomic.h>
> -#include <asm/hardirq.h>
>  #include <linux/netdevice.h>
>  #include <linux/in.h>
>  #include <linux/list.h>
> 

--
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>

  parent reply	other threads:[~2017-12-08  1:40 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
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 [this message]
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=4ed1efbc-5fb8-7412-4f46-1e3a91a98373@windriver.com \
    --to=ying.xue@windriver.com \
    --cc=davem@davemloft.net \
    --cc=jon.maloy@ericsson.com \
    --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).