linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the usb tree
Date: Tue, 18 May 2010 09:54:45 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1005180949560.1795-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20100518174253.37e38d66.sfr@canb.auug.org.au>

On Tue, 18 May 2010, Stephen Rothwell wrote:

> Hi Greg,
> 
> After merging the usb tree, today's linux-next build (powerpc
> ppc6xx_defconfig) failed like this:
> 
> drivers/usb/host/ehci-fsl.c:316: error: 'ehci' undeclared (first use in this function)
> 
> Caused by commit d19f8cd047971b43844d61d995be736dacb4826a ("USB: EHCI:
> fix controller wakeup flag settings during suspend").

Here's a fix for the problem.  It's awfully easy to mess things up when 
changing code for architectures you don't have.

Greg, can you merge this in with the original patch?

Alan Stern



Index: usb-2.6/drivers/usb/host/ehci-fsl.c
===================================================================
--- usb-2.6.orig/drivers/usb/host/ehci-fsl.c
+++ usb-2.6/drivers/usb/host/ehci-fsl.c
@@ -313,7 +313,7 @@ static int ehci_fsl_drv_suspend(struct d
 	struct ehci_fsl *ehci_fsl = hcd_to_ehci_fsl(hcd);
 	void __iomem *non_ehci = hcd->regs;
 
-	ehci_prepare_ports_for_controller_suspend(ehci);
+	ehci_prepare_ports_for_controller_suspend(hcd_to_ehci(hcd));
 	if (!fsl_deep_sleep())
 		return 0;
 

  reply	other threads:[~2010-05-18 13:54 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  7:42 linux-next: build failure after merge of the usb tree Stephen Rothwell
2010-05-18 13:54 ` Alan Stern [this message]
2010-05-18 14:08   ` Greg KH
2010-05-18 21:11   ` Greg KH
2010-05-19 22:49     ` Stephen Rothwell
2010-05-20  6:39       ` Greg KH
2010-05-18 14:00 ` Greg KH
2010-09-02  3:54 Stephen Rothwell
2010-09-02  4:32 ` Greg KH
2010-09-02  4:36   ` Michał Nazarewicz
2010-09-02  4:51   ` Stephen Rothwell
2010-09-14  2:54 Stephen Rothwell
2010-09-14  4:03 ` Greg KH
2010-09-14  4:08 ` Greg KH
2010-09-14  4:25   ` Stephen Rothwell
2010-09-14 13:26     ` Greg KH
2010-09-15 13:21     ` Mihai Donțu
2010-11-17  2:14 Stephen Rothwell
2010-11-17  4:20 ` Greg KH
     [not found]   ` <20101117042053.GB2999-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2010-11-17 15:56     ` Alan Stern
2010-11-17 21:25       ` Greg KH
2012-04-27  4:12 Stephen Rothwell
2012-04-27 18:25 ` Greg KH
2012-05-21  6:22 Stephen Rothwell
2012-05-21 12:56 ` Sarah Sharp
2012-09-19  4:31 Stephen Rothwell
2012-09-19  7:17 ` Greg KH
2012-09-19 13:59 ` Alan Cox
2012-09-19 14:13   ` Greg KH
2013-01-21  4:21 Stephen Rothwell
2013-01-21  8:37 ` Lan, Tianyu
2013-01-28 10:46 Stephen Rothwell
2013-01-28 14:45 ` Greg KH
2013-01-28 14:50   ` Lan Tianyu
2013-01-28 15:28   ` Lan Tianyu
2013-01-28 16:03   ` Lan, Tianyu
2013-01-29 13:41     ` Greg KH
2013-01-29 13:51       ` Lan, Tianyu
2013-01-29 14:59         ` Greg KH
2013-03-27  3:41 Stephen Rothwell
2013-03-27  3:51 ` Ming Lei
2013-03-27  4:20   ` Greg KH
2013-03-28 18:04 ` Greg KH
2013-04-18  6:05 Stephen Rothwell
2013-04-18 16:06 ` Joe Perches
2014-05-29  9:01 Stephen Rothwell
2014-05-29 18:18 ` Greg KH
2014-05-29 18:40   ` Dan Williams
2014-07-24  7:07 Stephen Rothwell
2014-07-24  7:44 ` Greg KH
2014-08-06  1:39   ` Stephen Rothwell
2014-08-06  4:04     ` Greg KH
2014-12-01  8:19 Stephen Rothwell
2014-12-02 18:12 ` Greg KH
2014-12-03  5:57   ` Kishon Vijay Abraham I
2019-06-19  6:43 Stephen Rothwell
2019-06-19 14:56 ` Greg KH
2020-03-16  3:10 Stephen Rothwell
2020-03-16 11:30 ` Thierry Reding
2020-03-16 13:28   ` Greg KH
2020-03-16 13:44     ` Thierry Reding
2021-04-12 11:36 Stephen Rothwell
2021-04-12 12:35 ` Greg KH
2021-04-12 12:41   ` Heikki Krogerus
2022-05-02 11:07 Stephen Rothwell
2022-05-02 11:40 ` Greg KH
2022-05-02 17:09   ` Matthias Kaehlcke
2022-05-02 17:32     ` Greg KH
2022-05-02 17:49       ` Matthias Kaehlcke
2022-05-03 14:49 ` Greg KH
2022-06-14  2:08 Stephen Rothwell
2022-06-14  2:41 ` Neal Liu
2022-06-14  6:30   ` Stephen Rothwell
2022-06-14  6:41 ` Greg KH
2022-06-14  7:52   ` Stephen Rothwell
2022-06-14  8:10     ` Bagas Sanjaya
2022-06-14  9:28       ` Greg KH
2022-06-14 11:11       ` Stephen Rothwell
2022-07-18  6:31 Stephen Rothwell
2022-07-18 20:43 ` Greg KH
2022-07-18 21:41   ` Prashant Malani
2022-07-18 22:08     ` Prashant Malani
2022-07-19  6:50     ` Greg KH
2022-07-19 12:01       ` Greg KH
2022-07-19 17:11         ` Prashant Malani
2022-07-19  6:08   ` Stephen Rothwell
2022-11-30  2:18 Stephen Rothwell
2022-11-30 10:52 ` Greg KH
2022-11-30 10:58   ` Andy Shevchenko
2022-11-30 17:43     ` Andy Shevchenko
2022-11-30 17:46       ` Greg KH
2022-11-30 10:53 ` Andy Shevchenko
2023-03-27  5:02 Stephen Rothwell
2023-03-27  7:37 ` Greg KH
2023-10-04  2:22 Stephen Rothwell
2023-10-04  6:43 ` Greg KH
2023-10-04  6:47   ` Rohit Agarwal
2023-10-04 12:46     ` Greg KH
2023-10-09  9:18       ` Rohit Agarwal
2023-10-09  9:48         ` Greg KH
2023-10-09  9:49           ` Dmitry Baryshkov
2023-10-12 17:03             ` Rohit Agarwal
2023-10-16 18:43               ` 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=Pine.LNX.4.44L0.1005180949560.1795-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=greg@kroah.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 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).