All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paul Zimmerman <Paul.Zimmerman@synopsys.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (staging tree related)
Date: Thu, 14 Mar 2013 13:33:53 -0700	[thread overview]
Message-ID: <20130314203353.GA16897@kroah.com> (raw)
In-Reply-To: <A2CA0424C0A6F04399FB9E1CD98E030458D8ED91@US01WEMBX2.internal.synopsys.com>

On Thu, Mar 14, 2013 at 08:23:39PM +0000, Paul Zimmerman wrote:
> > From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> > Sent: Tuesday, March 12, 2013 10:40 PM
> > 
> > After merging the final tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> > 
> > drivers/staging/dwc2/hcd.c: In function '_dwc2_hcd_urb_enqueue':
> > drivers/staging/dwc2/hcd.c:2387:3: error: implicit declaration of function 'bus_to_virt' [-Werror=implicit-function-declaration]
> > drivers/staging/dwc2/hcd.c:2387:7: warning: assignment makes pointer from integer without a cast [enabled by default]
> > 
> > Caused by commit 7359d482eb4d ("staging: HCD files for the DWC2 driver").
> > 
> > From Documentation/bus-virt-phys-mapping.txt:
> > 
> > "[ NOTE: The virt_to_bus() and bus_to_virt() functions have been
> >         superseded by the functionality provided by the PCI DMA interface
> >         (see Documentation/DMA-API-HOWTO.txt).  They continue
> >         to be documented below for historical purposes, but new code
> >         must not use them. --davidm 00/12/12 ]"
> > 
> > See also Documentation/DMA-API-HOWTO.txt.
> > 
> > I have added this patch for today:
> > 
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Wed, 13 Mar 2013 16:35:50 +1100
> > Subject: [PATCH] staging: the DWC2 driver uses bus_to_virt
> > 
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > ---
> >  drivers/staging/dwc2/Kconfig | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/staging/dwc2/Kconfig b/drivers/staging/dwc2/Kconfig
> > index 610418a..bc4cdfe 100644
> > --- a/drivers/staging/dwc2/Kconfig
> > +++ b/drivers/staging/dwc2/Kconfig
> > @@ -1,6 +1,7 @@
> >  config USB_DWC2
> >  	tristate "DesignWare USB2 DRD Core Support"
> >  	depends on USB
> > +	depends on VIRT_TO_BUS
> >  	select USB_OTG_UTILS
> >  	help
> >  	  Say Y or M here if your system has a Dual Role HighSpeed
> > --
> 
> Hi Greg,
> 
> Do you apply these sort of patches automatically, or do you need an ack from me?
> In case you do:
> 
> Acked-by: Paul Zimmerman <paulz@synopsys.com>

Thanks, I'll take it, I hadn't gotten to this fix just yet.

greg k-h

  reply	other threads:[~2013-03-14 20:33 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13  5:39 linux-next: build failure after merge of the final tree (staging tree related) Stephen Rothwell
2013-03-14 20:23 ` Paul Zimmerman
2013-03-14 20:33   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-10  4:54 Stephen Rothwell
2014-02-10  5:04 ` Greg KH
2013-06-19  8:10 Stephen Rothwell
2013-06-19  9:26 ` Peng Tao
2013-06-19 14:37   ` Greg KH
2013-06-20 10:52     ` Peng Tao
2013-06-24 22:40   ` Greg KH
2013-06-24 23:40     ` Stephen Rothwell
2013-06-24 23:50       ` Greg KH
2013-06-25  0:22         ` Peng Tao
2013-06-25  2:13           ` Greg KH
2013-04-24  7:56 linux-next: build failure after merge of the final tree (staging tree related)) Stephen Rothwell
2013-04-24 17:53 ` H Hartley Sweeten
2013-04-24 18:33 ` H Hartley Sweeten
2013-03-06  0:35 linux-next: build failure after merge of the final tree (staging tree related) Stephen Rothwell
2013-03-06  0:43 ` Greg KH
2013-03-06 13:56   ` Konrad Rzeszutek Wilk
2013-03-06 20:04     ` Konrad Rzeszutek Wilk
2013-03-06 20:46       ` Stephen Rothwell
2013-03-06 20:50       ` Stephen Rothwell
2013-03-06 22:23         ` Konrad Rzeszutek Wilk
2013-03-06 22:11       ` Greg KH
2013-03-06 22:21         ` Konrad Rzeszutek Wilk
2012-11-13  5:51 Stephen Rothwell
2012-11-13  9:24 ` Jonathan Cameron
2012-11-13 18:48 ` Greg KH
2012-09-24 14:29 Stephen Rothwell
2012-09-10  7:04 Stephen Rothwell
2012-09-10 17:31 ` Greg KH
2012-09-05  5:48 Stephen Rothwell
2012-09-06 18:06 ` Geert Uytterhoeven
2012-05-16 10:06 Stephen Rothwell
2012-05-16 12:49 ` Greg KH
2012-05-16 14:17   ` Dan Magenheimer
2012-05-16 15:10     ` Greg KH
2012-02-27  7:13 Stephen Rothwell
2012-02-27 21:16 ` Greg KH
2012-02-29  7:35   ` Chris Kelly
2012-02-29  7:52     ` Stephen Rothwell
2012-02-29 17:08       ` Chris Kelly
2012-02-13  6:19 Stephen Rothwell
2012-02-13  6:45 ` Greg KH
2012-02-13 14:13   ` Seth Jennings
2012-02-13 14:48   ` Seth Jennings
2012-02-13 15:03     ` Greg KH
2011-10-04  8:05 Stephen Rothwell
2011-10-04  8:49 ` Jonathan Cameron
2011-08-25  6:17 Stephen Rothwell
2011-08-24  5:47 Stephen Rothwell
2011-08-24 21:16 ` Greg KH
2011-08-24 22:54   ` Stephen Rothwell
2011-08-24 22:57     ` Greg KH
2011-08-24 23:28       ` Stephen Rothwell
2011-07-18  9:36 Stephen Rothwell
2011-07-19  1:01 ` Greg KH
2011-07-28  3:35   ` Stephen Rothwell
2011-08-02 23:17     ` Greg KH
2011-07-07  6:25 Stephen Rothwell
2011-07-07 13:44 ` Greg KH

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=20130314203353.GA16897@kroah.com \
    --to=greg@kroah.com \
    --cc=Paul.Zimmerman@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.