alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
	alsa-devel@alsa-project.org, Barry Song <barry.song@analog.com>,
	yi.li@analog.com, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [Uclinux-dist-devel] [PATCH 1/4] extend ad1938 codec driver to ad193x supporting ad1936/7/8/9
Date: Mon, 22 Mar 2010 13:50:08 +0800	[thread overview]
Message-ID: <3c17e3571003212250l5464504erb47f814319a28f6b@mail.gmail.com> (raw)
In-Reply-To: <20100319122422.GE23306@rakim.wolfsonmicro.main>

On Fri, Mar 19, 2010 at 8:24 PM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Fri, Mar 19, 2010 at 03:07:33PM +0800, Barry Song wrote:
>> It seems "git-format-patch -M" fails to detect this patch as a
>> rename(maybe due to too many changed lines?), so I commit two times to
>> get a readable patch and attach them.
>> 1. rename ad1938 to ad193x
>> 2. extend ad1938 codec driver to ad193x supporting ad1936/7/8/9
>
> Please don't top post and please always follow the patch submission
> procedure documented in Documentation/SubmittingPatches.  Even if
> problems with your MUA make it difficult to submit patches without using
> attachments you should always send one patch per message.  Not following
> these rules makes your patches much more difficult to handle.
>
> Since the patches aren't in line it's difficult to quote things when
> commenting but a few issues:
>
>  - Your rename patch didn't update the Makefile and Kconfig, which would
>   cause build breakage if applied alone.  You should always try to
>   ensure that builds work even with a partially applied patch series
>   since this allows things like bisection which step through the
>   history to work.
Yes. if i split into two patches, i should change Makefile and Kconfig
for the 1st one.

>
>  - You've left the bus_probe() functions exported - now you've merged
>   everything into one file this is no longer needed.
Yes. i noticed this too after i sent the patch.
>
>  - The way you've factored out the bus probe and removal functions so
>   that there's no code in the individual I2C and SPI functions means
>   that the register() and unregister() functions could just be squashed
>   into the bus_probe() and bus_remove() functions - all that the
>   register and unregister functions are is the code that's shared
>   between the bus
if so, it likes register/unregister should be moved into probe/remove
even for codecs with single codec?
>
> I've fixed the first issue by squashing the two patches together and the
> last one with a patch.  The last issue isn't important, it's more for
> information.
>
Thanks for your help to fix issues.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2010-03-22  5:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  8:16 [PATCH 0/4] extend ad1938 codec/machine driver to ad193x supporting ad1936/7/8/9 Barry Song
     [not found] ` <1268900221-6833-1-git-send-email-21cnbao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-03-18  8:16   ` [PATCH 1/4] extend ad1938 codec " Barry Song
     [not found]     ` <1268900221-6833-2-git-send-email-21cnbao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-03-18  8:16       ` [PATCH 2/4] change bf5xx-ad1938 machine driver to bf5xx-ad193x machine driver Barry Song
     [not found]         ` <1268900221-6833-3-git-send-email-21cnbao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-03-18  8:17           ` [PATCH 3/4] soc-cache: add i2c read entry for 8_8 mode Barry Song
2010-03-18  8:17             ` [PATCH 4/4] soc-cache: let reg be AND'ed by 0xff instead of data buffer " Barry Song
2010-03-18  9:00               ` Liam Girdwood
2010-03-18 11:30                 ` Mark Brown
2010-03-18  8:51             ` [PATCH 3/4] soc-cache: add i2c read entry " Liam Girdwood
2010-03-18 11:29               ` Mark Brown
2010-03-18 11:22         ` [PATCH 2/4] change bf5xx-ad1938 machine driver to bf5xx-ad193x machine driver Mark Brown
2010-03-18  8:48     ` [PATCH 1/4] extend ad1938 codec driver to ad193x supporting ad1936/7/8/9 Liam Girdwood
2010-03-18  9:08       ` Barry Song
2010-03-18 11:18         ` Mark Brown
2010-03-18 15:57           ` [Uclinux-dist-devel] " Mike Frysinger
2010-03-18 16:20             ` Mark Brown
2010-03-18 17:17               ` Mike Frysinger
2010-03-18 18:05                 ` Mark Brown
2010-03-18 18:08                   ` Mike Frysinger
2010-03-19  3:30                     ` Barry Song
2010-03-19  7:07                       ` Barry Song
2010-03-19  9:03                         ` Liam Girdwood
2010-03-19 12:24                         ` Mark Brown
2010-03-22  5:50                           ` Barry Song [this message]
2010-03-22 12:52                             ` 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=3c17e3571003212250l5464504erb47f814319a28f6b@mail.gmail.com \
    --to=21cnbao@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=barry.song@analog.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=yi.li@analog.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).