From: Dan Carpenter <dan.carpenter@oracle.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Sjur BRENDELAND <sjur.brandeland@stericsson.com>,
Fengguang Wu <fengguang.wu@intel.com>,
"Linus Walleij (linus.walleij@linaro.org)"
<linus.walleij@linaro.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [remoteproc:for-next 6/9] remoteproc_virtio.c:(.text+0x238e7e): undefined reference to `vring_tr
Date: Tue, 09 Oct 2012 14:26:45 +0000 [thread overview]
Message-ID: <20121009142644.GD4587@mwanda> (raw)
In-Reply-To: <CAK=WgbadhpEaP=ObM8rT=+xnEmh3xzb_ORThDfutH+jDOCf2mQ@mail.gmail.com>
On Tue, Oct 09, 2012 at 04:15:15PM +0200, Ohad Ben-Cohen wrote:
> On Tue, Oct 9, 2012 at 3:28 PM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> > Unless there is a good reason why
>
> That's what I'm asking. Is there an inherent coupling with some
> platform/architecture ? E.g., OMAP remote processors only go with
> OMAP chips.
If it already compiles fine on x86 then there is no advantage to
disabling it.
regards,
dan carpenter
next prev parent reply other threads:[~2012-10-09 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 2:45 [remoteproc:for-next 6/9] remoteproc_virtio.c:(.text+0x238e7e): undefined reference to `vring_transp Fengguang Wu
2012-10-02 8:24 ` [remoteproc:for-next 6/9] remoteproc_virtio.c:(.text+0x238e7e): undefined reference to `vring_tr Ohad Ben-Cohen
2012-10-09 9:56 ` Ohad Ben-Cohen
2012-10-09 10:30 ` Sjur BRENDELAND
2012-10-09 11:52 ` Ohad Ben-Cohen
2012-10-09 13:28 ` Dan Carpenter
2012-10-09 14:15 ` Ohad Ben-Cohen
2012-10-09 14:26 ` Dan Carpenter [this message]
2012-10-09 14:38 ` Ohad Ben-Cohen
2012-10-11 18:49 ` Sjur BRENDELAND
2012-10-11 21:08 ` Ohad Ben-Cohen
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=20121009142644.GD4587@mwanda \
--to=dan.carpenter@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=sjur.brandeland@stericsson.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