From: Kukjin Kim <kgene.kim@samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Kukjin Kim <kgene.kim@samsung.com>,
Ben Dooks <ben-linux@fluff.org>,
Sangbeom Kim <sbkim73@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: ASoC: samsung: MACH_SMDK6450
Date: Thu, 03 Jul 2014 07:37:07 +0900 [thread overview]
Message-ID: <53B48993.5020809@samsung.com> (raw)
In-Reply-To: <20140702092347.GB410@sirena.org.uk>
On 07/02/14 18:23, Mark Brown wrote:
> On Wed, Jul 02, 2014 at 09:47:18AM +0200, Paul Bolle wrote:
>
>> Your commit 0aeaa68cf509 ("ASoC: samsung: no more support for S5P6440
>> and S5P6450 SoCs") landed in next-20140702. It removed references to
>> MACH_SMDK6440 and MACH_SMDK6450 from sound/soc/samsung/.
>
Yeah, I missed the removing when I created the patch. Paul, thanks for
your pointing out and I'm resending the updated patch.
> This also wasn't sent to me for review, please always send patches to
> maintainers.
Mark, I always send patches to regarding maintainers and in this case
the patch missed the change. I'm resending new patch and if any
problems, please let me know. Just note, I just wanted to check whether
there is no problem with other maintainers' tree early in -next tree.
Thanks,
Kukjin
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: ASoC: samsung: MACH_SMDK6450
Date: Thu, 03 Jul 2014 07:37:07 +0900 [thread overview]
Message-ID: <53B48993.5020809@samsung.com> (raw)
In-Reply-To: <20140702092347.GB410@sirena.org.uk>
On 07/02/14 18:23, Mark Brown wrote:
> On Wed, Jul 02, 2014 at 09:47:18AM +0200, Paul Bolle wrote:
>
>> Your commit 0aeaa68cf509 ("ASoC: samsung: no more support for S5P6440
>> and S5P6450 SoCs") landed in next-20140702. It removed references to
>> MACH_SMDK6440 and MACH_SMDK6450 from sound/soc/samsung/.
>
Yeah, I missed the removing when I created the patch. Paul, thanks for
your pointing out and I'm resending the updated patch.
> This also wasn't sent to me for review, please always send patches to
> maintainers.
Mark, I always send patches to regarding maintainers and in this case
the patch missed the change. I'm resending new patch and if any
problems, please let me know. Just note, I just wanted to check whether
there is no problem with other maintainers' tree early in -next tree.
Thanks,
Kukjin
next prev parent reply other threads:[~2014-07-02 22:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 7:47 ASoC: samsung: MACH_SMDK6450 Paul Bolle
2014-07-02 7:47 ` Paul Bolle
2014-07-02 9:23 ` Mark Brown
2014-07-02 9:23 ` Mark Brown
2014-07-02 22:37 ` Kukjin Kim [this message]
2014-07-02 22:37 ` Kukjin Kim
2014-07-03 11:14 ` Mark Brown
2014-07-03 11:14 ` Mark Brown
2014-07-04 0:39 ` Kukjin Kim
2014-07-04 0:39 ` Kukjin Kim
2014-07-04 3:39 ` Olof Johansson
2014-07-04 3:39 ` Olof Johansson
2014-07-04 9:01 ` Arnd Bergmann
2014-07-04 9:01 ` Arnd Bergmann
2014-07-04 11:45 ` Mark Brown
2014-07-04 11:45 ` 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=53B48993.5020809@samsung.com \
--to=kgene.kim@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=perex@perex.cz \
--cc=sbkim73@samsung.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 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.