linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: "Chew, Kean Ho" <kean.ho.chew@intel.com>,
	"heikki.krogerus@linux.intel.com"
	<heikki.krogerus@linux.intel.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"jslaby@suse.cz" <jslaby@suse.cz>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [PATCHv2] serial: 8250: Add Quark X1000 to 8250 PCI driver
Date: Fri, 19 Sep 2014 14:25:39 +0100	[thread overview]
Message-ID: <541C2ED3.7080206@nexus-software.ie> (raw)
In-Reply-To: <1E478852902BF549B22CC4F16C2AE67C0F47241C@PGSMSX108.gar.corp.intel.com>

On 19/09/14 14:10, Chew, Kean Ho wrote:
>> Can you submit that soon
> Will do.
>
Hi Ho.

Do you have an idea when ?

I guess if we're saying the simple patch which works right now - should 
be rejected in favour of alternative code coming - then at a minimum 
could you please give an indication of when that alternative code will 
be available ?

Otherwise I think it makes sense to enable the hardware now - using the 
bog-standard means of doing that - just like BYT and others :)

-- 
BOD

  reply	other threads:[~2014-09-19 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19  7:43 [PATCHv2] serial: 8250: Add Quark X1000 to 8250 PCI driver Bryan O'Donoghue
2014-09-19 10:58 ` Heikki Krogerus
2014-09-19 11:34   ` Andy Shevchenko
2014-09-19 11:35   ` Bryan O'Donoghue
2014-09-19 12:06     ` Chew, Kean Ho
2014-09-19 13:02       ` Bryan O'Donoghue
2014-09-19 13:10         ` Chew, Kean Ho
2014-09-19 13:25           ` Bryan O'Donoghue [this message]
2014-09-19 14:31             ` Chew, Kean Ho
2014-09-19 15:38               ` Bryan O'Donoghue
2014-09-22  7:12 ` Heikki Krogerus

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=541C2ED3.7080206@nexus-software.ie \
    --to=pure.logic@nexus-software.ie \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jslaby@suse.cz \
    --cc=kean.ho.chew@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.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).