linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Felipe Balbi <balbi@kernel.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] usb: host: Enable compile testing for some of drivers
Date: Mon, 30 Dec 2019 21:06:18 +0100	[thread overview]
Message-ID: <20191230200618.GA1882713@kroah.com> (raw)
In-Reply-To: <20191230194249.GA26581@kozik-lap>

On Mon, Dec 30, 2019 at 08:42:49PM +0100, Krzysztof Kozlowski wrote:
> On Mon, Dec 30, 2019 at 08:36:21PM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Dec 30, 2019 at 08:29:56PM +0100, Greg Kroah-Hartman wrote:
> > > On Mon, Dec 30, 2019 at 06:22:14PM +0100, Krzysztof Kozlowski wrote:
> > > > Some of the USB host drivers can be compile tested to increase build
> > > > coverage.  Add 'if' conditional to 'default y' so they will not get
> > > > enabled by default on all other architectures.
> > > > 
> > > > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> > > > ---
> > > >  drivers/usb/host/Kconfig | 54 ++++++++++++++++++++--------------------
> > > >  1 file changed, 27 insertions(+), 27 deletions(-)
> > > 
> > > Nice, thanks for these, they should help out a lot with development.
> > 
> > And now I get this build warning with this patch:
> > 
> > WARNING: unmet direct dependencies detected for PHY_DA8XX_USB
> >   Depends on [n]: ARCH_DAVINCI_DA8XX
> >   Selected by [m]:
> >   - USB_OHCI_HCD_DAVINCI [=m] && USB_SUPPORT [=y] && USB [=m] && (ARCH_DAVINCI_DA8XX || COMPILE_TEST [=y]) && USB_OHCI_HCD [=m]
> > 
> > 
> > Care to provide a fix?
> 
> That's my fault. I was testing entire patchset which includes also other
> trees. I sent patch for PHY here:
> https://lore.kernel.org/lkml/20191230172449.17648-2-krzk@kernel.org/T/#u
> 
> Probably they should go together or we could ignore the error as it is
> only for build testing.

If that patchset gets merged, all is fine.  If not, let me know and I
can take it through my tree :)

thanks,

greg k-h

      reply	other threads:[~2019-12-30 20:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 17:22 [PATCH 1/2] usb: host: Enable compile testing for some of drivers Krzysztof Kozlowski
2019-12-30 17:22 ` [PATCH 2/2] usb: phy: " Krzysztof Kozlowski
2019-12-30 19:29 ` [PATCH 1/2] usb: host: " Greg Kroah-Hartman
2019-12-30 19:36   ` Greg Kroah-Hartman
2019-12-30 19:42     ` Krzysztof Kozlowski
2019-12-30 20:06       ` Greg Kroah-Hartman [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=20191230200618.GA1882713@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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;
as well as URLs for NNTP newsgroup(s).