From: Arend van Spriel <arend@broadcom.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Fu, Zhonghui" <zhonghui.fu@linux.intel.com>
Subject: Re: [PATCH] brcmfmac: fix invalid access to struct acpi_device fields
Date: Thu, 28 May 2015 20:31:02 +0200 [thread overview]
Message-ID: <55675EE6.4020505@broadcom.com> (raw)
In-Reply-To: <CAKf6xpuhDdRyQoYMxCQOkSvVzESkbWe=i4OvKm7C6hVRth6foA@mail.gmail.com>
On 05/28/15 18:48, Jason Andryuk wrote:
> On Wed, May 27, 2015 at 1:31 PM, Arend van Spriel<arend@broadcom.com> wrote:
>> diff --git a/drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c b/drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c
>> index b0d0ff5..71779b9 100644
>> --- a/drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c
>> +++ b/drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c
>> @@ -1117,6 +1117,18 @@ MODULE_DEVICE_TABLE(sdio, brcmf_sdmmc_ids);
>> static struct brcmfmac_sdio_platform_data *brcmfmac_sdio_pdata;
>>
>>
>> +static void brcmf_sdiod_acpi_set_power_manageable(struct device *dev,
>> + int val)
>> +{
>> +#if IS_ENABLED(CONFIG_ACPI)
>> + struct acpi_device *adev;
>> +
>> + adev = ACPI_COMPANION(dev);
>> + if (adev)
>> + adev->flags.power_manageable = 0;
>
> Shouldn't this be " = val"?
Definitely. The only place where it is called uses 0 for val parameter
so there is no big issue, but I will fix it.
Thanks for spotting that bit.
Regards,
Arend
> -Jason
>
>> +#endif
>> +}
>> +
>> static int brcmf_ops_sdio_probe(struct sdio_func *func,
>> const struct sdio_device_id *id)
>> {
prev parent reply other threads:[~2015-05-28 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 17:31 [PATCH] brcmfmac: fix invalid access to struct acpi_device fields Arend van Spriel
2015-05-28 8:29 ` Kalle Valo
2015-05-28 16:48 ` [PATCH] " Jason Andryuk
2015-05-28 18:31 ` Arend van Spriel [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=55675EE6.4020505@broadcom.com \
--to=arend@broadcom.com \
--cc=jandryuk@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zhonghui.fu@linux.intel.com \
/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).