From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Olof Johansson' <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [GIT PULL] cleanup samsung plat-s3c24xx and s5p for v3.5
Date: Tue, 15 May 2012 14:45:50 +0000 [thread overview]
Message-ID: <201205151445.50516.arnd@arndb.de> (raw)
In-Reply-To: <07f201cd3272$595ba050$0c12e0f0$%kim@samsung.com>
On Tuesday 15 May 2012, Kukjin Kim wrote:
> > I've pulled the next/cleanup-samsung-iommu into next/drivers and the
>
> But I think would be better if you could pull the next/devel-samsung-iommu into next/drivers instead of next/cleanup-samsung-iommu.
> Because actual iommu driver is included in next/devel-samsung-iommu branch and the next/cleanup-samsung-iommu branch includes just
> cleanup current Samsung iommu driver.
Ah, right. I though this was going through Jörg's IOMMU tree, but I saw now
that he agreed to having the new driver merged through arm-soc.
I've pulled both branches into next/drivers now.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] cleanup samsung plat-s3c24xx and s5p for v3.5
Date: Tue, 15 May 2012 14:45:50 +0000 [thread overview]
Message-ID: <201205151445.50516.arnd@arndb.de> (raw)
In-Reply-To: <07f201cd3272$595ba050$0c12e0f0$%kim@samsung.com>
On Tuesday 15 May 2012, Kukjin Kim wrote:
> > I've pulled the next/cleanup-samsung-iommu into next/drivers and the
>
> But I think would be better if you could pull the next/devel-samsung-iommu into next/drivers instead of next/cleanup-samsung-iommu.
> Because actual iommu driver is included in next/devel-samsung-iommu branch and the next/cleanup-samsung-iommu branch includes just
> cleanup current Samsung iommu driver.
Ah, right. I though this was going through J?rg's IOMMU tree, but I saw now
that he agreed to having the new driver merged through arm-soc.
I've pulled both branches into next/drivers now.
Arnd
next prev parent reply other threads:[~2012-05-15 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 23:18 [GIT PULL] cleanup samsung plat-s3c24xx and s5p for v3.5 Kukjin Kim
2012-05-12 23:18 ` Kukjin Kim
2012-05-13 5:21 ` Olof Johansson
2012-05-13 5:21 ` Olof Johansson
2012-05-14 7:38 ` Kukjin Kim
2012-05-14 7:38 ` Kukjin Kim
2012-05-14 19:17 ` Arnd Bergmann
2012-05-14 19:17 ` Arnd Bergmann
2012-05-15 8:11 ` Kukjin Kim
2012-05-15 8:11 ` Kukjin Kim
2012-05-15 14:45 ` Arnd Bergmann [this message]
2012-05-15 14:45 ` Arnd Bergmann
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=201205151445.50516.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--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.