From: Arnd Bergmann <arnd@arndb.de>
To: sundeep subbaraya <sundeep.lkml@gmail.com>
Cc: "balbi@ti.com" <balbi@ti.com>, Daniel Mack <daniel@zonque.org>,
Subbaraya Sundeep Bhatta <subbaraya.sundeep.bhatta@xilinx.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michal Simek <michals@xilinx.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
svemula@xilinx.com, anirudh@xilinx.com,
Subbaraya Sundeep Bhatta <sbhatta@xilinx.com>
Subject: Re: [PATCH v4 2/2] usb: gadget: Add xilinx usb2 device support
Date: Wed, 10 Sep 2014 16:30:50 +0200 [thread overview]
Message-ID: <8798156.X6RhQq9Iqm@wuerfel> (raw)
In-Reply-To: <CALHRZuqt-XJ5mPczzGJtSN=iq7TPut0=54r90QHWR+w-Lwwtyg@mail.gmail.com>
On Wednesday 10 September 2014 19:25:11 sundeep subbaraya wrote:
> > that's not exactly what I asked Usually you only add COMPILE_TEST
> > when you have an ARCH dependency. So something like:
> >
> > depends on ARCH_ARM || COMPILE_TEST
> >
> > would make it clear that this driver is only available on ARM, but when
> > doing my build tests, I'd still be able to compile it on x86.
>
> Ok got it
Most of the xilinx stuff also applies to MICROBLAZE however, so it
may need to be
ARM || MICROBLAZE || COMPILE_TEST
(not ARCH_ARM, btw).
> >> > Also, your code uses device tree functions unconditionally, which is
> >> > fine, but it must hence depend on 'OF'.
> >>
> >> Ok will add OF along with COMPILE_TEST
> >
> > so this would be:
> >
> > depends on OF || COMPILE_TEST
If it requires OF to build, you can use 'OF && (ARM || COMPILE_TEST)',
but if there is no compile-time dependency, you can just leave out
the 'depends on OF' completely. You can't even build a Zynq machine
without OF enabled.
Arnd
prev parent reply other threads:[~2014-09-10 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1406020130-20467-1-git-send-email-sbhatta@xilinx.com>
[not found] ` <1406020130-20467-1-git-send-email-sbhatta-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2014-07-22 9:08 ` [PATCH v4 2/2] usb: gadget: Add xilinx usb2 device support Subbaraya Sundeep Bhatta
[not found] ` <31c3ad1a-370a-4d0d-b392-8e7bb292f6aa-reflc3kr++NQO6Rm7zmc1+hlVc3/7hDbVaz/vdPVXQ4@public.gmane.org>
2014-07-22 10:02 ` Varka Bhadram
[not found] ` <53CE36C2.50307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-08-19 6:08 ` sundeep subbaraya
2014-08-19 9:56 ` Daniel Mack
[not found] ` <53F31F52.8060904-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>
2014-08-19 10:08 ` Daniel Mack
2014-08-21 6:49 ` sundeep subbaraya
[not found] ` <CALHRZur5BC8Q2WFghU8jAtXzt1=tm=8swxp2xEz3MV4z5CCE9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 14:00 ` Felipe Balbi
[not found] ` <20140821140040.GE9608-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2014-09-10 13:55 ` sundeep subbaraya
2014-09-10 14:30 ` Arnd Bergmann [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=8798156.X6RhQq9Iqm@wuerfel \
--to=arnd@arndb.de \
--cc=anirudh@xilinx.com \
--cc=balbi@ti.com \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=sbhatta@xilinx.com \
--cc=subbaraya.sundeep.bhatta@xilinx.com \
--cc=sundeep.lkml@gmail.com \
--cc=svemula@xilinx.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