linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yang Shi" <yang.s@alibaba-inc.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
	Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 6/8] net: caif: remove unused hardirq.h
Date: Fri, 08 Dec 2017 03:13:55 +0800	[thread overview]
Message-ID: <9ad5b35a-8d4c-448a-912b-2816c4c8c53f@alibaba-inc.com> (raw)
In-Reply-To: <1510959741-31109-6-git-send-email-yang.s@alibaba-inc.com>

Hi folks,

Any comment on this one?

Thanks,
Yang


On 11/17/17 3:02 PM, Yang Shi wrote:
> Preempt counter APIs have been split out, currently, hardirq.h just
> includes irq_enter/exit APIs which are not used by caif at all.
> 
> So, remove the unused hardirq.h.
> 
> Signed-off-by: Yang Shi <yang.s@alibaba-inc.com>
> Cc: Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>
> Cc: "David S. Miller" <davem@davemloft.net>
> ---
>   net/caif/cfpkt_skbuff.c | 1 -
>   net/caif/chnl_net.c     | 1 -
>   2 files changed, 2 deletions(-)
> 
> diff --git a/net/caif/cfpkt_skbuff.c b/net/caif/cfpkt_skbuff.c
> index 71b6ab2..38c2b7a 100644
> --- a/net/caif/cfpkt_skbuff.c
> +++ b/net/caif/cfpkt_skbuff.c
> @@ -8,7 +8,6 @@
>   
>   #include <linux/string.h>
>   #include <linux/skbuff.h>
> -#include <linux/hardirq.h>
>   #include <linux/export.h>
>   #include <net/caif/cfpkt.h>
>   
> diff --git a/net/caif/chnl_net.c b/net/caif/chnl_net.c
> index 922ac1d..53ecda1 100644
> --- a/net/caif/chnl_net.c
> +++ b/net/caif/chnl_net.c
> @@ -8,7 +8,6 @@
>   #define pr_fmt(fmt) KBUILD_MODNAME ":%s(): " fmt, __func__
>   
>   #include <linux/fs.h>
> -#include <linux/hardirq.h>
>   #include <linux/init.h>
>   #include <linux/module.h>
>   #include <linux/netdevice.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>

  reply	other threads:[~2017-12-07 19:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 23:02 [PATCH 1/8] mm: kmemleak: " 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 [this message]
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=9ad5b35a-8d4c-448a-912b-2816c4c8c53f@alibaba-inc.com \
    --to=yang.s@alibaba-inc.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.tarnyagin@lockless.no \
    --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 \
    /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