From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: hverkuil@xs4all.nl, mchehab@redhat.com, sameo@linux.intel.com,
perex@perex.cz, tiwai@suse.de, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 7/7] sound/soc/codecs: Cosmetic changes to SI476X codec driver
Date: Wed, 20 Feb 2013 17:11:43 +0000 [thread overview]
Message-ID: <20130220171142.GQ2726@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1361246375-8848-8-git-send-email-andrew.smirnov@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
On Mon, Feb 18, 2013 at 07:59:35PM -0800, Andrey Smirnov wrote:
> - Add appropriate license header
> - Change email address in MODULE_AUTHOR
> - Remove trailing whitespaces
Applied, thanks. Always use subject lines appropriate for the subsystem
you're submitting against.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-02-20 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 3:59 [PATCH v4 0/7] Driver for Si476x series of chips Andrey Smirnov
2013-02-19 3:59 ` [PATCH v4 1/7] mfd: Add header files and Kbuild plumbing for SI476x MFD core Andrey Smirnov
2013-02-19 3:59 ` [PATCH v4 2/7] mfd: Add commands abstraction layer for SI476X MFD Andrey Smirnov
2013-02-19 3:59 ` [PATCH v4 3/7] mfd: Add the main bulk of core driver for SI476x code Andrey Smirnov
2013-02-19 3:59 ` [PATCH v4 4/7] mfd: Add chip properties handling code for SI476X MFD Andrey Smirnov
2013-02-19 3:59 ` [PATCH v4 5/7] v4l2: Add a V4L2 driver " Andrey Smirnov
2013-02-19 3:59 ` [PATCH v4 6/7] sound/soc/codecs: Convert SI476X codec to use regmap Andrey Smirnov
2013-02-20 17:11 ` Mark Brown
2013-02-19 3:59 ` [PATCH v4 7/7] sound/soc/codecs: Cosmetic changes to SI476X codec driver Andrey Smirnov
2013-02-20 17:11 ` Mark Brown [this message]
2013-02-19 5:05 ` [PATCH v4 0/7] Driver for Si476x series of chips Hans Verkuil
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=20130220171142.GQ2726@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=andrew.smirnov@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=perex@perex.cz \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).