From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Reddy, MR Swami" <MR.Swami.Reddy@nsc.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: Add National Semiconductor LM49352 Audio Codec support
Date: Mon, 7 Mar 2011 13:18:14 +0000 [thread overview]
Message-ID: <20110307131814.GJ13471@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <290463D19D2E064191F1F96ECA480A89432CB6D84E@EXMAIL02.scwf.nsc.com>
On Mon, Mar 07, 2011 at 04:03:55AM -0800, Reddy, MR Swami wrote:
Please fix your MUA to word wrap within paragraphs at less than 80
columns. I've reflowed your mail for legibility. There are some
suggestions in Documentation/email-clients.txt.
> Patch for adding National Semiconductor LM49352 Audio Codec (http://www.national.com/ds/LM/LM49352.pdf) support along with Samsung_6410 (i.e. SMDK6410) platform support for LM49352.
> [Tested this patch on SMDK6410 platform with Kernel- 2.6.24 and ALSA version is - 1.0.15].
> Please review and let me know the comments/suggestion on this patch.
You need to follow the standard kernel patch submission process, which
is documented in Documentation/SubmittingPatches. In particular you
should:
- Conform to the coding standards in CodingStandards (checkpatch.pl is
helpful for detecting obvious issues). A good high level check is if
your code should visually resemble the rest of the code base.
- Submit your code against the current development kernel version. The
trees will be listed in MAINTAINERS, or -next is a good approximation.
- Send your patch in-line rather than as an attachment.
- Send your patch against the full Linux tree, not a subdirectory of
it.
You should also split your code up into a series of independant patches
- in general each individual driver should be a single patch so your
machine and CODEC drivers should be split up. If the machine driver is
just for a flying wire system you should remove it, otherwise please
also submit the arch/arm parts.
I've not done a detailed review of the code due to the above high level
issues.
> And also let me know the forward-porting (to the latest ALSA version APIs) steps/process. Thanks in advance.
You need to figure out a process that works for you. In general
inspecting the kernel history is usually very useful for stuff like
this, or you could just start from scratch and copy over the active bits
of code.
next prev parent reply other threads:[~2011-03-07 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 12:03 [PATCH] ASoC: Add National Semiconductor LM49352 Audio Codec support Reddy, MR Swami
2011-03-07 13:18 ` Mark Brown [this message]
2011-03-08 4:31 ` Reddy, MR Swami
2011-03-16 7:38 ` [PATCH] ASoC: Add National Semiconductor LM49352 Codec Support Reddy, MR Swami
2011-03-16 10:08 ` Mark Brown
2011-03-16 13:38 ` Reddy, MR Swami
2011-03-16 14:35 ` Mark Brown
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=20110307131814.GJ13471@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=MR.Swami.Reddy@nsc.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
/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).