From: Paul Bolle <pebolle@tiscali.nl>
To: Sachin Kamat <sachin.kamat@linaro.org>, Olof Johansson <olof@lixom.net>
Cc: Richard Weinberger <richard@nod.at>,
Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 04/28] Remove EXYNOS_DEV_SYSMMU
Date: Tue, 15 Apr 2014 11:33:16 +0200 [thread overview]
Message-ID: <1397554396.1985.31.camel@x220> (raw)
In-Reply-To: <CAK9yfHzP0ekboc-yi6FHvR3_rRiqcLC18pE2UynpxGYO0mUOsw@mail.gmail.com>
On Mon, 2014-02-10 at 10:02 +0530, Sachin Kamat wrote:
> +cc linux-samsung-soc list
>
> On 10 February 2014 01:38, Paul Bolle <pebolle@tiscali.nl> wrote:
> > I noted this one about a year ago (see
> > https://lkml.org/lkml/2013/3/5/401 ). By now I wonder whether
> > EXYNOS_IOMMU (and everything depending on it) shouldn't be removed. That
> > code has been unbuildable for at least a year now (I have not checked
> > how much code is involved).
>
>
> Please refer to some on-going discussion about it at [1].
>
> [1] http://thread.gmane.org/gmane.linux.kernel.samsung-soc/26842
It's not clear to me whether an actual decision was eventually made.
Olof, does it make sense to rebase the patch (that Sachin linked to) on
onto v3.15-rc1 and resubmit?
Paul Bolle
next prev parent reply other threads:[~2014-04-15 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1391971686-9517-1-git-send-email-richard@nod.at>
2014-02-09 18:47 ` [PATCH 04/28] Remove EXYNOS_DEV_SYSMMU Richard Weinberger
[not found] ` <1391971686-9517-5-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2014-02-09 20:08 ` Paul Bolle
2014-02-10 4:32 ` Sachin Kamat
2014-04-15 9:33 ` Paul Bolle [this message]
2014-02-09 18:47 ` [PATCH 10/28] Remove SH_MOBILE Richard Weinberger
[not found] ` <1391971686-9517-11-git-send-email-richard-/L3Ra7n9ekc@public.gmane.org>
2014-02-09 20:32 ` Paul Bolle
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=1397554396.1985.31.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=richard@nod.at \
--cc=sachin.kamat@linaro.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