From: Kukjin Kim <kgene.kim@samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: Olof Johansson <olof@lixom.net>,
Kukjin Kim <kgene.kim@samsung.com>,
"arm@kernel.org" <arm@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [GIT PULL] Samsung cleanup for S5P SoCs for 3.17
Date: Sun, 13 Jul 2014 07:34:30 +0900 [thread overview]
Message-ID: <53C1B7F6.7050803@samsung.com> (raw)
In-Reply-To: <20140712194416.GA6800@sirena.org.uk>
On 07/13/14 04:44, Mark Brown wrote:
> On Sat, Jul 12, 2014 at 09:59:48AM -0700, Olof Johansson wrote:
>
>> I've merged these in. I noticed lack of acked-by from Mark Brown, so I pinged
>> him on IRC about it and the branch is currently at the top so it's easy to drop
>> in case he has objections (cc:d here too).
>
> Don't know if I've seen these changes (though IIRC they might've gone to
> the work account). I suspect we're going to get some conflicts since
> we've also got other changes going on in ASoC so it is probably going to
> be easier to merge at least that patch via ASoC.
OK.
Olof, I will resend the pull-request after sorting them out so please
drop this then pull new one.
Mark, please take following ASoC related patches.
- ASoC: samsung: no more support for S5P6440 and S5P6450 SoCs
- ASoC: Samsung: remove s5pc100 related codes
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: [GIT PULL] Samsung cleanup for S5P SoCs for 3.17
Date: Sun, 13 Jul 2014 07:34:30 +0900 [thread overview]
Message-ID: <53C1B7F6.7050803@samsung.com> (raw)
In-Reply-To: <20140712194416.GA6800@sirena.org.uk>
On 07/13/14 04:44, Mark Brown wrote:
> On Sat, Jul 12, 2014 at 09:59:48AM -0700, Olof Johansson wrote:
>
>> I've merged these in. I noticed lack of acked-by from Mark Brown, so I pinged
>> him on IRC about it and the branch is currently at the top so it's easy to drop
>> in case he has objections (cc:d here too).
>
> Don't know if I've seen these changes (though IIRC they might've gone to
> the work account). I suspect we're going to get some conflicts since
> we've also got other changes going on in ASoC so it is probably going to
> be easier to merge at least that patch via ASoC.
OK.
Olof, I will resend the pull-request after sorting them out so please
drop this then pull new one.
Mark, please take following ASoC related patches.
- ASoC: samsung: no more support for S5P6440 and S5P6450 SoCs
- ASoC: Samsung: remove s5pc100 related codes
Thanks,
Kukjin
next prev parent reply other threads:[~2014-07-12 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 22:59 [GIT PULL] Samsung cleanup for S5P SoCs for 3.17 Kukjin Kim
2014-07-07 22:59 ` Kukjin Kim
2014-07-12 16:59 ` Olof Johansson
2014-07-12 16:59 ` Olof Johansson
2014-07-12 19:44 ` Mark Brown
2014-07-12 19:44 ` Mark Brown
2014-07-12 22:34 ` Kukjin Kim [this message]
2014-07-12 22:34 ` Kukjin Kim
2014-07-12 22:43 ` [GIT PULL] Samsung cleanup 2nd version " Kukjin Kim
2014-07-12 22:43 ` Kukjin Kim
2014-07-13 4:22 ` Olof Johansson
2014-07-13 4:22 ` Olof Johansson
2014-07-13 4:20 ` [GIT PULL] Samsung cleanup " Olof Johansson
2014-07-13 4:20 ` Olof Johansson
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=53C1B7F6.7050803@samsung.com \
--to=kgene.kim@samsung.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/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.