linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@nxp.com>
To: Baolin Wang <baolin.wang7@gmail.com>
Cc: Felipe Balbi <balbi@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	"pawell@cadence.com" <pawell@cadence.com>,
	"rogerq@ti.com" <rogerq@ti.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: RE: [PATCH 1/1] usb: cdns3: add NXP imx8qm glue layer
Date: Fri, 3 Jan 2020 03:20:17 +0000	[thread overview]
Message-ID: <VI1PR04MB53274DD899A84806D84C5FBB8B230@VI1PR04MB5327.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CADBw62roaEi6UWV3X2NtqQ55w_SONactEn=JxrPShMV7oj98vQ@mail.gmail.com>

 
> > Hi Felipe,
> >
> > How to make sure it works? Except for enabling CONFIG_COMPLIE_TEST,
> > what else I need to do? Thanks.
> 
> Felipe's suggestion is you should change your config dependency as:
> depends on ARCH_MXC || COMPILE_TEST
> 
> Then user can compile your driver to find warning or something else though the
> ARCH_MXC config is not enabled.

Hi Baolin,

I know that, I have already changed that,  unset ARCH_MXC and enable
CONFIG_COMPILE_TEST. What else I could do to make sure it could compile OK
at every architecture?

Peter

  reply	other threads:[~2020-01-03  3:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27  5:59 [PATCH 1/1] usb: cdns3: add NXP imx8qm glue layer Peter Chen
2020-01-02 11:26 ` Felipe Balbi
2020-01-03  2:31   ` Peter Chen
2020-01-03  2:41     ` Baolin Wang
2020-01-03  3:20       ` Peter Chen [this message]
2020-01-03  3:35         ` Baolin Wang
2020-01-03  8:44         ` gregkh
2020-01-03  9:26         ` Felipe Balbi
2020-01-03 13:36 ` Roger Quadros
2020-01-06  2:45   ` Peter Chen

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=VI1PR04MB53274DD899A84806D84C5FBB8B230@VI1PR04MB5327.eurprd04.prod.outlook.com \
    --to=peter.chen@nxp.com \
    --cc=balbi@kernel.org \
    --cc=baolin.wang7@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=pawell@cadence.com \
    --cc=rogerq@ti.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;
as well as URLs for NNTP newsgroup(s).