From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
matthias@kaehlcke.net, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 3/3] sound/soc/soc-core.c: drop kfree of devm_kzalloc's data
Date: Mon, 10 Dec 2012 16:09:28 +0900 [thread overview]
Message-ID: <20121210070927.GK10927@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212100709450.2213@localhost6.localdomain6>
On Mon, Dec 10, 2012 at 07:10:16AM +0100, Julia Lawall wrote:
> Sorry, I just resent the patch as is. 1 and 2 were I guess applied,
> because I odn't findthe problem any more.
It looks like this is what happened the first time round as well - I
only got patch 3 but it was flagged as part of a three patch series.
Please don't do things like this, it makes the patch look like part of a
series which has already been applied but didn't get deleted when it's
sitting in an inbox.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
matthias@kaehlcke.net, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 3/3] sound/soc/soc-core.c: drop kfree of devm_kzalloc's data
Date: Mon, 10 Dec 2012 07:09:28 +0000 [thread overview]
Message-ID: <20121210070927.GK10927@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212100709450.2213@localhost6.localdomain6>
On Mon, Dec 10, 2012 at 07:10:16AM +0100, Julia Lawall wrote:
> Sorry, I just resent the patch as is. 1 and 2 were I guess applied,
> because I odn't findthe problem any more.
It looks like this is what happened the first time round as well - I
only got patch 3 but it was flagged as part of a three patch series.
Please don't do things like this, it makes the patch look like part of a
series which has already been applied but didn't get deleted when it's
sitting in an inbox.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Liam Girdwood <lrg@ti.com>,
matthias@kaehlcke.net, kernel-janitors@vger.kernel.org,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] sound/soc/soc-core.c: drop kfree of devm_kzalloc's data
Date: Mon, 10 Dec 2012 16:09:28 +0900 [thread overview]
Message-ID: <20121210070927.GK10927@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212100709450.2213@localhost6.localdomain6>
On Mon, Dec 10, 2012 at 07:10:16AM +0100, Julia Lawall wrote:
> Sorry, I just resent the patch as is. 1 and 2 were I guess applied,
> because I odn't findthe problem any more.
It looks like this is what happened the first time round as well - I
only got patch 3 but it was flagged as part of a three patch series.
Please don't do things like this, it makes the patch look like part of a
series which has already been applied but didn't get deleted when it's
sitting in an inbox.
next prev parent reply other threads:[~2012-12-10 7:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 12:00 [PATCH 3/3] sound/soc/soc-core.c: drop kfree of devm_kzalloc's data Julia Lawall
2012-08-04 12:00 ` Julia Lawall
2012-08-04 12:00 ` Julia Lawall
2012-08-04 14:32 ` Mark Brown
2012-08-04 14:32 ` Mark Brown
2012-08-04 14:32 ` Mark Brown
2012-12-08 17:01 ` Julia Lawall
2012-12-08 18:01 ` Julia Lawall
2012-12-10 5:23 ` Mark Brown
2012-12-10 5:23 ` Mark Brown
2012-12-10 6:10 ` Julia Lawall
2012-12-10 6:10 ` Julia Lawall
2012-12-10 6:10 ` Julia Lawall
2012-12-10 7:09 ` Mark Brown [this message]
2012-12-10 7:09 ` Mark Brown
2012-12-10 7:09 ` Mark Brown
2012-12-10 7:18 ` Mark Brown
2012-12-10 7:18 ` 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=20121210070927.GK10927@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=matthias@kaehlcke.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.