Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@redhat.com>
To: zhongjiang@huawei.com
Cc: netanel@amazon.com, jcliburn@gmail.com, chris.snook@gmail.com,
	santosh@chelsio.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: remove redundant include
Date: Tue, 18 Sep 2018 20:08:33 -0700 (PDT)	[thread overview]
Message-ID: <20180918.200833.893204273871606035.davem@redhat.com> (raw)
In-Reply-To: <1537258213-43522-1-git-send-email-zhongjiang@huawei.com>

From: zhong jiang <zhongjiang@huawei.com>
Date: Tue, 18 Sep 2018 16:10:13 +0800

> module.h already contained moduleparam.h,  so it is safe to remove
> the redundant include.
> 
> The issue is detected with the help of Coccinelle.
> 
> Signed-off-by: zhong jiang <zhongjiang@huawei.com>

Applied.

      reply	other threads:[~2018-09-19  3:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-18  8:10 [PATCH] net: ethernet: remove redundant include zhong jiang
2018-09-19  3:08 ` David Miller [this message]

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=20180918.200833.893204273871606035.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=chris.snook@gmail.com \
    --cc=jcliburn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netanel@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=santosh@chelsio.com \
    --cc=zhongjiang@huawei.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