From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Mark Brown' <broonie@kernel.org>
Cc: 'Paul Bolle' <pebolle@tiscali.nl>,
'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: Fri, 04 Jul 2014 09:39:06 +0900 [thread overview]
Message-ID: <023d01cf9720$5ed32fc0$1c798f40$@samsung.com> (raw)
In-Reply-To: <20140703111442.GW410@sirena.org.uk>
Mark Brown wrote:
>
> On Thu, Jul 03, 2014 at 07:37:07AM +0900, Kukjin Kim wrote:
> > On 07/02/14 18:23, Mark Brown wrote:
>
> > >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.
>
> It looks like you've sent it to broonie@linaro.org not broonie@kernel.org
> which is listed in MAINTAINERS and what I use for e-mail - upstream mail
> that goes to my work address often just gets dropped on the floor (and
> generally ends up at the bottom of my queue to look at) since it ends up
> in a completely different place to my personal mail.
Mark, oh, I see. But I checked your e-mail address from recent your sign-off
in git commit so, just thought it should be fine.
I will use kernel.org for your e-mail address next time ;-)
And you have any comments or ack on the series, please kindly let me know.
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: Fri, 04 Jul 2014 09:39:06 +0900 [thread overview]
Message-ID: <023d01cf9720$5ed32fc0$1c798f40$@samsung.com> (raw)
In-Reply-To: <20140703111442.GW410@sirena.org.uk>
Mark Brown wrote:
>
> On Thu, Jul 03, 2014 at 07:37:07AM +0900, Kukjin Kim wrote:
> > On 07/02/14 18:23, Mark Brown wrote:
>
> > >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.
>
> It looks like you've sent it to broonie at linaro.org not broonie at kernel.org
> which is listed in MAINTAINERS and what I use for e-mail - upstream mail
> that goes to my work address often just gets dropped on the floor (and
> generally ends up at the bottom of my queue to look at) since it ends up
> in a completely different place to my personal mail.
Mark, oh, I see. But I checked your e-mail address from recent your sign-off
in git commit so, just thought it should be fine.
I will use kernel.org for your e-mail address next time ;-)
And you have any comments or ack on the series, please kindly let me know.
Thanks,
Kukjin
next prev parent reply other threads:[~2014-07-04 0:39 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
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 [this message]
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='023d01cf9720$5ed32fc0$1c798f40$@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.