From: Jonathan Corbet <corbet@lwn.net>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: linux-kernel@vger.kernel.org, Peter Foley <pefoley2@pefoley.com>,
Siva Yerramreddy <yshivakrishna@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, Sudeep Dutt <sudeep.dutt@intel.com>,
Caz Yokoyama <Caz.Yokoyama@intel.com>,
Daniel Borkmann <dborkman@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nikhil Rao <nikhil.rao@intel.com>,
linuxppc-dev@lists.ozlabs.org,
Jennings <sjennings@variantweb.net>,
Dan Streetman <ddstreet@ieee.org>,
Dasaratharaman Chandramouli
<dasaratharaman.chandramouli@intel.com>
Subject: Re: [PATCH linux-next] Documentation: Build mic/mpssd only for x86_64
Date: Fri, 5 Dec 2014 11:18:18 -0500 [thread overview]
Message-ID: <20141205111818.551a870f@lwn.net> (raw)
In-Reply-To: <25c04eb72c621fc9bdf0aae25782ff5bad5a4b97.1417728278.git.ashutosh.dixit@intel.com>
On Thu, 4 Dec 2014 13:27:29 -0800
Ashutosh Dixit <ashutosh.dixit@intel.com> wrote:
> mic/mpssd along with MIC drivers are currently only usable on
> x86_64. So build mic/mpssd only for x86_64 to avoid build breaks on
> big-endian systems.
I can certainly apply this. But it seems to me that this kind of code
doesn't belong in the documentation directory. How about a patch to move
it to tools/ ?
jon
next prev parent reply other threads:[~2014-12-05 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 21:27 [PATCH linux-next] Documentation: Build mic/mpssd only for x86_64 Ashutosh Dixit
2014-12-05 3:27 ` Dan Streetman
2014-12-05 18:18 ` Ashutosh Dixit
2014-12-05 19:53 ` Dan Streetman
2014-12-05 16:18 ` Jonathan Corbet [this message]
2014-12-05 18:26 ` Ashutosh Dixit
2014-12-05 18:29 ` Ashutosh Dixit
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=20141205111818.551a870f@lwn.net \
--to=corbet@lwn.net \
--cc=Caz.Yokoyama@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=dborkman@redhat.com \
--cc=ddstreet@ieee.org \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nikhil.rao@intel.com \
--cc=pefoley2@pefoley.com \
--cc=rdunlap@infradead.org \
--cc=sjennings@variantweb.net \
--cc=sudeep.dutt@intel.com \
--cc=yshivakrishna@gmail.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