From: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public•gmane.org>
To: lud <linux-usb-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public•gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0@public•gmane.org>
Subject: Re: linux-next: Tree for February 21 (usb/serial)
Date: Thu, 3 Mar 2011 13:51:52 -0800 [thread overview]
Message-ID: <20110303135152.c4b53da1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <201102212130.01789.rjw-KKrjLPT3xs0@public.gmane.org>
On Mon, 21 Feb 2011 21:30:01 +0100 Rafael J. Wysocki wrote:
> On Monday, February 21, 2011, Randy Dunlap wrote:
> > On Mon, 21 Feb 2011 18:21:34 +1100 Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > Changes since 20110218:
> >
> >
> > When CONFIG_PM_RUNTIME is not enabled:
> >
> > drivers/usb/serial/usb_wwan.c:702: error: 'struct dev_pm_info' has no member named 'usage_count'
>
> This looks like a bug in the driver that shouldn't access this field directly.
This build error is still with us in linux-next 2011.0303.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-03 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 7:21 linux-next: Tree for February 21 Stephen Rothwell
2011-02-21 17:57 ` linux-next: Tree for February 21 (usb/serial) Randy Dunlap
2011-02-21 20:30 ` Rafael J. Wysocki
[not found] ` <201102212130.01789.rjw-KKrjLPT3xs0@public.gmane.org>
2011-03-03 21:51 ` Randy Dunlap [this message]
2011-03-04 15:04 ` Alan Stern
2011-03-15 15:36 ` Randy Dunlap
2011-02-21 22:39 ` [PATCH -next] staging: fix olpc_dcon kconfig and build errors Randy Dunlap
2011-02-22 5:29 ` Andres Salomon
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=20110303135152.c4b53da1.randy.dunlap@oracle.com \
--to=randy.dunlap-qhclzuegtsvqt0dzr+alfa@public$(echo .)gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=rjw-KKrjLPT3xs0@public$(echo .)gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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