public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Purna Chandra Mandal <purna.mandal@microchip.com>,
	linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-usb@vger.kernel.org,
	Joshua Henderson <digitalpeer@digitalpeer.com>,
	Cristian Birsan <cristian.birsan@microchip.com>,
	Purna Chandra Mandal <purna.mandal@microchip.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Bin Liu <b-liu@ti.com>, Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v2 2/2] usb: musb: pic32: Add USB DRC driver for PIC32 OTG controller.
Date: Thu, 07 Apr 2016 15:39:57 +0300	[thread overview]
Message-ID: <874mbdr3s2.fsf@intel.com> (raw)
In-Reply-To: <1460032381-32677-2-git-send-email-purna.mandal@microchip.com>

[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]

Purna Chandra Mandal <purna.mandal@microchip.com> writes:
> From: Cristian Birsan <cristian.birsan@microchip.com>
>
> This driver adds support of PIC32 MUSB OTG controller as
> dual role device. It implements platform specific glue to
> reuse musb core.
>
> Signed-off-by: Cristian Birsan <cristian.birsan@microchip.com>
> Signed-off-by: Purna Chandra Mandal <purna.mandal@microchip.com>
>
> In-reply-to: 460027775-20729-2-git-send-email-purna.mandal@microchip.com
>
> ---
>
> Changes in v2:
>  - fix i386 build
>  - fix indentation
>
>  drivers/usb/musb/Kconfig  |   9 +-
>  drivers/usb/musb/Makefile |   1 +
>  drivers/usb/musb/pic32.c  | 608 ++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 617 insertions(+), 1 deletion(-)
>  create mode 100644 drivers/usb/musb/pic32.c
>
> diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
> index 886526b..1970c1e 100644
> --- a/drivers/usb/musb/Kconfig
> +++ b/drivers/usb/musb/Kconfig
> @@ -112,6 +112,13 @@ config USB_MUSB_BLACKFIN
>  	depends on (BF54x && !BF544) || (BF52x && ! BF522 && !BF523)
>  	depends on NOP_USB_XCEIV
>  
> +config USB_MUSB_PIC32
> +	tristate "Microchip PIC32 USB platforms"
> +	depends on MACH_PIC32

no, we like to build stuff on other arches, this should be:

	depends on MACH_PIC32 || COMPILE_TEST

and you should *really* fix the build error, not work around it.

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2016-04-07 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <460027775-20729-2-git-send-email-purna.mandal@microchip.com>
2016-04-07 12:32 ` [PATCH v2 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver Purna Chandra Mandal
2016-04-07 12:33   ` [PATCH v2 2/2] usb: musb: pic32: Add USB DRC driver for PIC32 OTG controller Purna Chandra Mandal
2016-04-07 12:39     ` Felipe Balbi [this message]
2016-04-07 12:53       ` Purna Chandra Mandal
2016-04-08  5:38         ` Felipe Balbi
2016-04-07 13:34   ` [PATCH v2 1/2] dt/bindings/usb: Add bindings for PIC32 MUSB driver Sergei Shtylyov
2016-04-07 13:34     ` Purna Chandra Mandal
2016-04-11 15:10   ` Rob Herring
2016-04-12 10:15     ` Purna Chandra Mandal

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=874mbdr3s2.fsf@intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=b-liu@ti.com \
    --cc=cristian.birsan@microchip.com \
    --cc=digitalpeer@digitalpeer.com \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=purna.mandal@microchip.com \
    --cc=robh+dt@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