From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC updates for 3.2
Date: Thu, 22 Dec 2011 12:46:56 +0000 [thread overview]
Message-ID: <20111222124655.GO4546@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAAQ0ZWTnMuDCHDQQWg9mvQHTwzm6hJu5TOFvbwc18R5xEhSdiw@mail.gmail.com>
On Thu, Dec 22, 2011 at 08:38:39PM +0800, Shawn Guo wrote:
> On 22 December 2011 20:02, Mark Brown
> > If the API change is only in -next this shouldn't have been applied to
> > the ASoC tree at all. This needs go along with the change that adds the
> > new API otherwise you break bisection. Things like this *really* need
> > to be made clear when posting patches.
> I did mention that the patch series addresses the issue seen on -next
> tree in the cover letter. And I replied your query as below.
You shouldn't rely on cover letters getting noticed, they're too easy to
disassociate from the patch.
> > With patches like this you really need to supply more context - knowing
> > which release the commit you're talking about appears in is useful for
> > exammple,
> This patch only applies to -next, as the offending patch only sits on
> -next.
Yeah, that was after I'd applied the patch.
TBH given that this is an incompatible API change the original patch
relly ought to be updating all users, there shouldn't be separate
patches for the drivers.
next prev parent reply other threads:[~2011-12-22 12:46 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 11:04 ASoC updates for 3.2 Mark Brown
2011-12-22 11:15 ` Takashi Iwai
[not found] ` <CAAQ0ZWSoQJJZv9ReBvHC1FB2EeS_u2V=jDJOguoqNx2cR+1i_g@mail.gmail.com>
2011-12-22 12:02 ` Mark Brown
2011-12-22 12:07 ` Takashi Iwai
[not found] ` <CAAQ0ZWTnMuDCHDQQWg9mvQHTwzm6hJu5TOFvbwc18R5xEhSdiw@mail.gmail.com>
2011-12-22 12:46 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-13 1:40 Mark Brown
2011-12-13 7:06 ` Takashi Iwai
2011-12-13 7:09 ` Mark Brown
2011-12-06 10:16 Mark Brown
2011-12-06 12:26 ` Takashi Iwai
2011-11-30 10:28 Mark Brown
2011-11-30 11:20 ` Takashi Iwai
2011-11-29 11:36 Mark Brown
2011-11-29 12:07 ` Takashi Iwai
2011-11-22 12:46 Mark Brown
2011-11-22 17:47 ` Takashi Iwai
2011-11-08 10:46 Mark Brown
2011-11-08 16:00 ` Takashi Iwai
2011-11-02 11:50 Mark Brown
2011-11-02 13:16 ` Takashi Iwai
2011-11-02 13:17 ` Mark Brown
2011-11-02 13:23 ` Takashi Iwai
2011-10-27 7:22 Mark Brown
2011-10-27 8:49 ` Takashi Iwai
2011-10-22 9:49 Mark Brown
2011-10-22 11:45 ` Takashi Iwai
2011-10-19 17:26 Mark Brown
2011-10-20 12:20 ` Takashi Iwai
2011-10-20 12:24 ` Mark Brown
2011-10-20 12:47 ` Takashi Iwai
2011-10-20 16:56 ` Girdwood, Liam
2011-10-13 10:49 Mark Brown
2011-10-13 10:53 ` Takashi Iwai
2011-10-10 11:41 Mark Brown
2011-10-10 12:42 ` Takashi Iwai
2011-10-10 12:46 ` Mark Brown
2011-10-04 14:16 Mark Brown
2011-10-04 14:45 ` Takashi Iwai
2011-10-04 14:48 ` Mark Brown
2011-10-04 14:49 ` Takashi Iwai
2011-09-27 12:47 Mark Brown
2011-09-27 13:01 ` Takashi Iwai
2011-09-23 10:47 Mark Brown
2011-09-23 13:23 ` Takashi Iwai
2011-09-20 14:43 Mark Brown
2011-09-20 14:47 ` Takashi Iwai
2011-09-08 18:23 Mark Brown
2011-08-25 11:08 Mark Brown
2011-08-25 12:08 ` Takashi Iwai
2011-08-21 12:10 Mark Brown
2011-08-21 13:47 ` Takashi Iwai
2011-08-12 16:51 Mark Brown
2011-08-12 17:50 ` Takashi Iwai
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=20111222124655.GO4546@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=shawn.guo@linaro.org \
--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).