All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Peter Chen <peter.chen@nxp.com>, Baolin Wang <baolin.wang7@gmail.com>
Cc: "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, 03 Jan 2020 11:26:40 +0200	[thread overview]
Message-ID: <87y2uoki0f.fsf@kernel.org> (raw)
In-Reply-To: <VI1PR04MB53274DD899A84806D84C5FBB8B230@VI1PR04MB5327.eurprd04.prod.outlook.com>

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


Hi,

Peter Chen <peter.chen@nxp.com> writes:
>  
>> > 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?

If it works fine on ARM and x86 it's rather unlikely that it will break
anywhere else. In any case, once I apply the patch to my tree, it will
be compiled by 0-day build service in several different architectures.

-- 
balbi

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

  parent reply	other threads:[~2020-01-03  9:26 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
2020-01-03  3:35         ` Baolin Wang
2020-01-03  8:44         ` gregkh
2020-01-03  9:26         ` Felipe Balbi [this message]
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=87y2uoki0f.fsf@kernel.org \
    --to=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=peter.chen@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.