All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
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 17:28:00 +0100	[thread overview]
Message-ID: <20100426172800.5405f352@linux.intel.com> (raw)
In-Reply-To: <20100426162202.GA11755@srcf.ucam.org>

> 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.

As has already been pointed out large parts of the enabling code are
already merged into other bits of the kernel.

Alan

  reply	other threads:[~2010-04-26 17:04 UTC|newest]

Thread overview: 16+ 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 [this message]
2010-04-26 17:06             ` Matthew Garrett
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
2010-04-09 10:29 Alan Cox
2010-04-21 20:16 ` Andrew Morton
2010-04-21 20:26   ` Alan Cox
2010-04-22 13:16   ` Alan Cox
2010-04-22 13:41     ` Andrew Morton

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=20100426172800.5405f352@linux.intel.com \
    --to=alan@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=mjg59@srcf.ucam.org \
    --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 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.