From: David Miller <davem@davemloft•net>
To: inaky@linux•intel.com
Cc: netdev@vger•kernel.org, wimax@linuxwimax•org, greg@kroah•com,
randy.dunlap@oracle•com, sfr@canb•auug.org.au,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-wimax@intel•com
Subject: Re: [PATCH 4/4] i2400m/usb: wrap USB power saving in #ifdef CONFIG_PM
Date: Thu, 08 Jan 2009 11:08:35 -0800 (PST) [thread overview]
Message-ID: <20090108.110835.109199764.davem@davemloft.net> (raw)
In-Reply-To: <0e511f3772ac9887551bec34ee682fa5bf63fb69.1231355768.git.inaky@linux.intel.com>
From: Inaky Perez-Gonzalez <inaky@linux•intel.com>
Date: Wed, 7 Jan 2009 11:22:22 -0800
> Current code was assuming PM was always enabled, which is not
> correct. Code which accesses members in the struct usb_device that are
> dependant on CONFIG_PM must be protected the same.
>
> Reported by Randy Dunlap from a build error in the linux-next tree on
> 07/01/2009.
>
> Signed-off-by: Inaky Perez-Gonzalez <inaky@linux•intel.com>
Also applied, thanks a lot.
next prev parent reply other threads:[~2009-01-08 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 19:22 [PATCH 0/4] wimax: Kbuild / rfkill-build / PM fixes (v3) Inaky Perez-Gonzalez
2009-01-07 19:22 ` [PATCH 1/4] wimax: fix '#ifndef CONFIG_BUG' layout to avoid warning Inaky Perez-Gonzalez
2009-01-08 19:07 ` David Miller
2009-01-07 19:22 ` [PATCH 2/4] wimax: fix kconfig interactions with rfkill and input layers Inaky Perez-Gonzalez
2009-01-08 19:07 ` David Miller
2009-01-07 19:22 ` [PATCH 3/4] wimax: testing for rfkill support should also test for CONFIG_RFKILL_MODULE Inaky Perez-Gonzalez
2009-01-08 19:08 ` David Miller
2009-01-07 19:22 ` [PATCH 4/4] i2400m/usb: wrap USB power saving in #ifdef CONFIG_PM Inaky Perez-Gonzalez
2009-01-08 19:08 ` David Miller [this message]
2009-01-08 0:10 ` [PATCH 0/4] wimax: Kbuild / rfkill-build / PM fixes (v3) Randy Dunlap
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=20090108.110835.109199764.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=greg@kroah$(echo .)com \
--cc=inaky@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wimax@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=wimax@linuxwimax$(echo .)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