From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Wolfram Sang <wsa@the-dreams.de>, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v1 1/1] i2c-i801: make it depend on CONFIG_X86
Date: Fri, 17 Jun 2016 22:05:54 +0300 [thread overview]
Message-ID: <1466190354.30123.163.camel@linux.intel.com> (raw)
In-Reply-To: <20160617205936.74d3c6cd@endymion>
On Fri, 2016-06-17 at 20:59 +0200, Jean Delvare wrote:
> On Fri, 17 Jun 2016 12:31:35 +0300, Andy Shevchenko wrote:
> > On Thu, 2016-06-16 at 11:49 +0200, Jean Delvare wrote:
> > > depends on X86 || IA64 || COMPILE_TEST
> >
> > I don't like this. (...)
>
> May I ask why?
>From my point of view it's not scalable. If new arch comes you have to
add it here.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2016-06-17 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 13:22 [PATCH v1 1/1] i2c-i801: make it depend on CONFIG_X86 Andy Shevchenko
2016-06-16 9:49 ` Jean Delvare
2016-06-17 9:31 ` Andy Shevchenko
2016-06-17 18:59 ` Jean Delvare
2016-06-17 19:05 ` Andy Shevchenko [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=1466190354.30123.163.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).