From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: Intel: remove duplicate headers
Date: Tue, 13 May 2014 12:30:40 +0300 [thread overview]
Message-ID: <5371E640.7030007@linux.intel.com> (raw)
In-Reply-To: <1399969755-15976-1-git-send-email-andriy.shevchenko@linux.intel.com>
On 05/13/2014 11:29 AM, Andy Shevchenko wrote:
> A few files contain duplicate headers. This patch removes the second entry of
> duplicate in each file under question.
>
> There is no functional changes.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> sound/soc/intel/sst-baytrail-ipc.c | 1 -
> sound/soc/intel/sst-haswell-ipc.c | 1 -
> sound/soc/intel/sst-haswell-pcm.c | 1 -
> 3 files changed, 3 deletions(-)
>
>
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
prev parent reply other threads:[~2014-05-13 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 8:29 [PATCH] ASoC: Intel: remove duplicate headers Andy Shevchenko
2014-05-13 9:30 ` Jarkko Nikula [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=5371E640.7030007@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.de \
/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