From: Kukjin Kim <kgene@kernel.org>
To: 'Javier Martinez Canillas' <javier@dowhile0.org>,
'Kukjin Kim' <kgene@kernel.org>
Cc: arm@kernel.org, 'Arnd Bergmann' <arnd@arndb.de>,
'Olof Johansson' <olof@lixom.net>,
'Kevin Hilman' <khilman@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
'Javier Martinez Canillas' <javier.martinez@collabora.co.uk>
Subject: RE: [GIT PULL 2/5] Samsung defconfig udpates for v4.1
Date: Mon, 06 Apr 2015 15:49:02 +0900 [thread overview]
Message-ID: <023d01d07035$c499b650$4dcd22f0$@kernel.org> (raw)
In-Reply-To: <CABxcv=kHPaJE4WGUHsgBPnFpT4aYqiodHVnTn+AccUhu3Te-Jw@mail.gmail.com>
Javier Martinez Canillas wrote:
>
> Hello Kukjin,
>
Hi,
> On Wed, Apr 1, 2015 at 8:16 PM, Kukjin Kim <kgene@kernel.org> wrote:
> > The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
> >
> > Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > tags/samsung-defconfig
> >
> > for you to fetch changes up to bb84296ae52da844c9cab81e0197152a69f2f841:
> >
> > ARM: exynos_defconfig: Enable HDMI support (2015-03-27 02:00:09 +0900)
> >
> > ----------------------------------------------------------------
> > Samsung defconfig updates for v4.1
> >
> > - update exynos-defconfig
> > : enable HDMI, CPUidle, ChromeOS EC chardev driver
> > and thermal emulation, Marvell WiFi-Ex, CPUfreq,
> > and support for NFS rootfs
> > : remove EXYNOS_THERMAL_CORE define
> > and disable IOMMU support until support it
> >
> > ----------------------------------------------------------------
> > Javier Martinez Canillas (5):
> > ARM: exynos_defconfig: Disable IOMMU support
>
> As I mentioned before, this also is needed for 4.0-rc to have display
> working on at least Exynos5420 Peach Pit and Exynos5800 Peach Pi
> Chromebooks but I saw that it is not included in your "Samsung 2nd
> fixes for v4.0" git pull [0].
>
Yeah, you're right. The 'disabling IOMMU' should be queued for 4.0-rc but I've
missed. Sorry about that. As you know, the branch has been queued for 4.1
already so if we send it even the one patch for 4.0-rc, it will cause conflict.
So I think would be better if we could send it to stable after 4.1-rc1? If you
agree, I'll.
> Maybe it can be sent directly to arm@kernel.org?
>
I don't think so because of above reason...
- Kukjin
WARNING: multiple messages have this Message-ID (diff)
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/5] Samsung defconfig udpates for v4.1
Date: Mon, 06 Apr 2015 15:49:02 +0900 [thread overview]
Message-ID: <023d01d07035$c499b650$4dcd22f0$@kernel.org> (raw)
In-Reply-To: <CABxcv=kHPaJE4WGUHsgBPnFpT4aYqiodHVnTn+AccUhu3Te-Jw@mail.gmail.com>
Javier Martinez Canillas wrote:
>
> Hello Kukjin,
>
Hi,
> On Wed, Apr 1, 2015 at 8:16 PM, Kukjin Kim <kgene@kernel.org> wrote:
> > The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
> >
> > Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > tags/samsung-defconfig
> >
> > for you to fetch changes up to bb84296ae52da844c9cab81e0197152a69f2f841:
> >
> > ARM: exynos_defconfig: Enable HDMI support (2015-03-27 02:00:09 +0900)
> >
> > ----------------------------------------------------------------
> > Samsung defconfig updates for v4.1
> >
> > - update exynos-defconfig
> > : enable HDMI, CPUidle, ChromeOS EC chardev driver
> > and thermal emulation, Marvell WiFi-Ex, CPUfreq,
> > and support for NFS rootfs
> > : remove EXYNOS_THERMAL_CORE define
> > and disable IOMMU support until support it
> >
> > ----------------------------------------------------------------
> > Javier Martinez Canillas (5):
> > ARM: exynos_defconfig: Disable IOMMU support
>
> As I mentioned before, this also is needed for 4.0-rc to have display
> working on at least Exynos5420 Peach Pit and Exynos5800 Peach Pi
> Chromebooks but I saw that it is not included in your "Samsung 2nd
> fixes for v4.0" git pull [0].
>
Yeah, you're right. The 'disabling IOMMU' should be queued for 4.0-rc but I've
missed. Sorry about that. As you know, the branch has been queued for 4.1
already so if we send it even the one patch for 4.0-rc, it will cause conflict.
So I think would be better if we could send it to stable after 4.1-rc1? If you
agree, I'll.
> Maybe it can be sent directly to arm at kernel.org?
>
I don't think so because of above reason...
- Kukjin
next prev parent reply other threads:[~2015-04-06 6:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 18:16 [GIT PULL 2/5] Samsung defconfig udpates for v4.1 Kukjin Kim
2015-04-01 18:16 ` Kukjin Kim
2015-04-03 21:58 ` Olof Johansson
2015-04-03 21:58 ` Olof Johansson
2015-04-04 6:47 ` Javier Martinez Canillas
2015-04-04 6:47 ` Javier Martinez Canillas
2015-04-06 6:49 ` Kukjin Kim [this message]
2015-04-06 6:49 ` Kukjin Kim
2015-04-06 7:49 ` Javier Martinez Canillas
2015-04-06 7:49 ` Javier Martinez Canillas
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='023d01d07035$c499b650$4dcd22f0$@kernel.org' \
--to=kgene@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=javier.martinez@collabora.co.uk \
--cc=javier@dowhile0.org \
--cc=khilman@linaro.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.