From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: zhong jiang <zhongjiang@huawei.com>
Cc: <broonie@kernel.org>, <lgirdwood@gmail.com>,
<oder_chiou@realtek.com>, <bardliao@realtek.com>,
<perex@perex.cz>, <tiwai@suse.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: remove redundant include
Date: Tue, 18 Sep 2018 09:38:31 +0100 [thread overview]
Message-ID: <20180918083831.GL1653@imbe.wolfsonmicro.main> (raw)
In-Reply-To: <1537258584-43853-1-git-send-email-zhongjiang@huawei.com>
On Tue, Sep 18, 2018 at 04:16:24PM +0800, zhong jiang wrote:
> 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>
> ---
For the Wolfson bits:
Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
prev parent reply other threads:[~2018-09-18 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 8:16 [PATCH] ASoC: remove redundant include zhong jiang
2018-09-18 8:38 ` Charles Keepax [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=20180918083831.GL1653@imbe.wolfsonmicro.main \
--to=ckeepax@opensource.cirrus.com \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).