From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung cleanup 2nd version for S5P SoCs for 3.17
Date: Sat, 12 Jul 2014 21:22:37 -0700 [thread overview]
Message-ID: <20140713042237.GA14206@quad.lixom.net> (raw)
In-Reply-To: <53C1BA14.8060903@samsung.com>
On Sun, Jul 13, 2014 at 07:43:32AM +0900, Kukjin Kim wrote:
> (changed title)
>
> Hi,
>
> As per Mark's suggestion, I'm re-sending the cleanup S5P SoCs for
> v3.17 so please take this instead.
>
> One more, I dropped serial related patches also because they also
> will be handled via Greg's tty tree for 3.17.
>
> Thanks and if any problems, please let me know.
>
> - Kukjin
>
> ------------------
> The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
>
> Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> tags/s5p-cleanup-v2
>
> for you to fetch changes up to f86e0add813a3cc0e338089fa6c0928f5f6dc52d:
>
> video: fbdev: s3c-fb: remove s5pc100 related fimd and fb codes
> (2014-07-13 07:35:15 +0900)
>
> ----------------------------------------------------------------
> Cleanup S5P SoCs for 3.17
> - removing s5p64x0 SoCs and s5pc100 SoC in mainline because
> no more user and if it is required next time, it will be
> supported with DT.
Pulled, thanks!
-Olof
next prev parent reply other threads:[~2014-07-13 4:22 UTC|newest]
Thread overview: 7+ 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-12 16:59 ` Olof Johansson
2014-07-12 19:44 ` Mark Brown
2014-07-12 22:34 ` Kukjin Kim
2014-07-12 22:43 ` [GIT PULL] Samsung cleanup 2nd version " Kukjin Kim
2014-07-13 4:22 ` Olof Johansson [this message]
2014-07-13 4:20 ` [GIT PULL] Samsung cleanup " 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=20140713042237.GA14206@quad.lixom.net \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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