From: Jean Delvare <jdelvare@suse.de>
To: Alan Cox <alan@linux.intel.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: SERIAL_MRST_MAX3110 should depend on X86_MRST
Date: Tue, 27 Sep 2011 14:10:16 +0200 [thread overview]
Message-ID: <201109271410.16584.jdelvare@suse.de> (raw)
In-Reply-To: <20110927120115.376b3c31@bob.linux.org.uk>
On Tuesday 27 September 2011 01:01:15 pm Alan Cox wrote:
> On Fri, 16 Sep 2011 22:40:16 +0200
>
> Jean Delvare <jdelvare@suse.de> wrote:
> > As I understand it, driver mrst_max3110 is only useful on
> > Moorestown systems, so it should depend on X86_MRST.
>
> Digging into this it builds fine on any X86 so it's more useful that
> it is able to get build tested than to add extra config stuff making
> it hard to catch bugs when changing the serial layer.
OK, fair enough.
--
Jean Delvare
Suse L3
prev parent reply other threads:[~2011-09-27 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 20:40 [PATCH] serial: SERIAL_MRST_MAX3110 should depend on X86_MRST Jean Delvare
2011-09-17 11:28 ` Alan Cox
2011-09-27 11:01 ` Alan Cox
2011-09-27 12:10 ` Jean Delvare [this message]
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=201109271410.16584.jdelvare@suse.de \
--to=jdelvare@suse.de \
--cc=alan@linux.intel.com \
--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).