From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Cox <alan@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org, akpm@linux-foundation.org,
sreedhara.ds@intel.com, mingo@elte.hu
Subject: Re: [PATCH] IPC driver for Intel Mobile Internet Device (MID) platforms
Date: Mon, 26 Apr 2010 18:06:16 +0100 [thread overview]
Message-ID: <20100426170616.GA12769@srcf.ucam.org> (raw)
In-Reply-To: <20100426172800.5405f352@linux.intel.com>
On Mon, Apr 26, 2010 at 05:28:00PM +0100, Alan Cox wrote:
> > I'm really not terribly comfortable merging enabling code for an
> > architecture if there's no clear plan for merging critical parts of
> > that architecture.
>
> I'm not interested in playing graphics driver politics. If I could do
> something short term about the graphics situation I would. Furthermore
> there isn't anything I can do about it (even if it does involve its
> own *clean* mode setting to keep KeithP from exploding) until the
> core merges are done.
It's been pointed out to me that there are non-graphical targets for
this platform as well, so in that case there's no real argument on my
side. I'll queue this for .35.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-04-26 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 14:30 [PATCH] IPC driver for Intel Mobile Internet Device (MID) platforms Alan Cox
2010-04-26 15:09 ` Matthew Garrett
2010-04-26 14:55 ` Alan Cox
2010-04-26 15:43 ` Matthew Garrett
2010-04-26 15:39 ` Alan Cox
2010-04-26 16:22 ` Matthew Garrett
2010-04-26 16:28 ` Alan Cox
2010-04-26 17:06 ` Matthew Garrett [this message]
2010-04-26 17:13 ` Alan Cox
2010-05-07 18:25 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2010-04-21 12:25 Alan Cox
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=20100426170616.GA12769@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=mingo@elte.hu \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sreedhara.ds@intel.com \
/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