From: Randy Dunlap <rdunlap@infradead.org>
To: wei_wang@realsil.com.cn
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] linux-next:usb-stor:realtek_cr:Fix compile error
Date: Sun, 28 Apr 2013 15:22:27 -0700 [thread overview]
Message-ID: <517DA123.10005@infradead.org> (raw)
In-Reply-To: <1367030953-24707-1-git-send-email-wei_wang@realsil.com.cn>
On 04/26/13 19:49, wei_wang@realsil.com.cn wrote:
> From: Wei WANG <wei_wang@realsil.com.cn>
>
> To fix the compile error when CONFIG_PM_RUNTIME is not enabled,
> move the declaration of us out of CONFIG_REALTEK_AUTOPM macro in rts51x_chip.
>
> drivers/usb/storage/realtek_cr.c: In function 'realtek_cr_destructor':
> drivers/usb/storage/realtek_cr.c:942:11: error: 'struct rts51x_chip' has no member named 'us'
>
> Signed-off-by: Wei WANG <wei_wang@realsil.com.cn>
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/usb/storage/realtek_cr.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/storage/realtek_cr.c b/drivers/usb/storage/realtek_cr.c
> index 4797228..64c2b28 100644
> --- a/drivers/usb/storage/realtek_cr.c
> +++ b/drivers/usb/storage/realtek_cr.c
> @@ -105,8 +105,9 @@ struct rts51x_chip {
> int status_len;
>
> u32 flag;
> -#ifdef CONFIG_REALTEK_AUTOPM
> struct us_data *us;
> +
> +#ifdef CONFIG_REALTEK_AUTOPM
> struct timer_list rts51x_suspend_timer;
> unsigned long timer_expires;
> int pwr_state;
> @@ -991,6 +992,7 @@ static int init_realtek_cr(struct us_data *us)
> us->extra = chip;
> us->extra_destructor = realtek_cr_destructor;
> us->max_lun = chip->max_lun = rts51x_get_max_lun(us);
> + chip->us = us;
>
> usb_stor_dbg(us, "chip->max_lun = %d\n", chip->max_lun);
>
> @@ -1013,10 +1015,8 @@ static int init_realtek_cr(struct us_data *us)
> SET_AUTO_DELINK(chip);
> }
> #ifdef CONFIG_REALTEK_AUTOPM
> - if (ss_en) {
> - chip->us = us;
> + if (ss_en)
> realtek_cr_autosuspend_setup(us);
> - }
> #endif
>
> usb_stor_dbg(us, "chip->flag = 0x%x\n", chip->flag);
>
--
~Randy
prev parent reply other threads:[~2013-04-28 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 2:49 [PATCH] linux-next:usb-stor:realtek_cr:Fix compile error wei_wang
2013-04-28 22:22 ` Randy Dunlap [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=517DA123.10005@infradead.org \
--to=rdunlap@infradead.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=wei_wang@realsil.com.cn \
/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).