From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/2] ommu/exynos: Add IOMMU/System MMU driver for Samsung Exynos
Date: Wed, 4 Jan 2012 21:26:20 +0000 [thread overview]
Message-ID: <20120104212620.GG11810@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120104150101.GA3492@amd.com>
On Wed, Jan 04, 2012 at 04:01:01PM +0100, Joerg Roedel wrote:
> On Tue, Jan 03, 2012 at 09:55:27AM +0000, Russell King - ARM Linux wrote:
> > It comes through when I stick it in my tree because of a month of asking
> > for help to fix something and getting zero response from the maintainers.
> >
> > It's a way to flag to them that they're doing something wrong - and in
> > fact something is broken, and that that brokenness will happen at the
> > next merge window unless they get off their butt and do something about
> > it.
>
> Okay, fine with me if it really will be fixed in 3.3-rc1 :)
I can do better than that - and report that it's fixed now. It should
show up in linux-next sometime after Stephen pulls this evening. The
#error did its job in this case, and ensured that it got fixed!
next prev parent reply other threads:[~2012-01-04 21:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 12:24 [PATCH v8 0/2] ommu/exynos: Add IOMMU/System MMU driver for Samsung Exynos KyongHo Cho
2012-01-02 13:42 ` Joerg Roedel
2012-01-02 15:21 ` KyongHo Cho
2012-01-02 15:58 ` Joerg Roedel
2012-01-03 1:02 ` Kukjin Kim
2012-01-03 8:15 ` KyongHo Cho
2012-01-03 9:55 ` Russell King - ARM Linux
2012-01-04 15:01 ` Joerg Roedel
2012-01-04 21:26 ` Russell King - ARM Linux [this message]
2012-01-05 11:47 ` Joerg Roedel
2012-01-09 0:32 ` KyongHo Cho
2012-01-02 16:35 ` Joerg Roedel
2012-01-03 9:37 ` Marek Szyprowski
2012-01-03 13:10 ` 'Joerg Roedel'
2012-02-24 13:45 ` Marek Szyprowski
2012-02-24 16:08 ` KyongHo Cho
2012-02-27 15:51 ` Marek Szyprowski
2012-02-27 16:04 ` KyongHo Cho
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=20120104212620.GG11810@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).