From: Okash Khawaja <okash.khawaja@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Peter Rosin <peda@lysator.liu.se>,
"kvalo@codeaurora.org" <kvalo@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] adm8211: fix checkpatch errors for indentation and new line around switch-case
Date: Tue, 5 May 2015 15:15:16 +0100 [thread overview]
Message-ID: <8BB992B7-F9AE-4D3E-92DC-E9154785C92F@gmail.com> (raw)
In-Reply-To: <1430833852.7191.7.camel@perches.com>
> On 5 May 2015, at 14:50, Joe Perches <joe@perches.com> wrote:
>
> On Tue, 2015-05-05 at 14:03 +0200, Peter Rosin wrote:
>>> diff --git a/drivers/net/wireless/adm8211.c b/drivers/net/wireless/adm8211.c
> []
>>> @@ -1098,14 +1098,18 @@ static void adm8211_hw_init(struct ieee80211_hw *dev)
>>> pci_read_config_byte(priv->pdev, PCI_CACHE_LINE_SIZE, &cline);
>>>
>>> switch (cline) {
> []
>>> + case 0x8:
>>> + reg |= (0x1 << 14);
>>> + break;
>>> + case 0x16:
>>> + reg |= (0x2 << 14);
>>> + break;
>>> + case 0x32:
>>> + reg |= (0x3 << 14);
>>> + break;
>>> + default:
>>> + reg |= (0x0 << 14);
>>> + break;
>>> }
>>> }
>>
>> Those 0x16/0x32 hexadecimal case-selectors looking suspiciously like
>> decimal bits need a comment if they are in fact correct, which I doubt.
>
> Good spot.
>
> As it's testing PCI_CACHE_LINE_SIZE,
> they seem very much broken.
>
>
Interesting. I'll be happy to fix that bit if someone could guide me on it. Looks like these values should be 0x10, 0x20 instead of 0x16, 0x32 respectively. But I am unable to understand their meaning in this code.
Thanks
next prev parent reply other threads:[~2015-05-05 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 11:37 Okash Khawaja
2015-05-05 12:03 ` Peter Rosin
2015-05-05 13:50 ` Joe Perches
2015-05-05 14:15 ` Okash Khawaja [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-05 11:25 Okash Khawaja
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=8BB992B7-F9AE-4D3E-92DC-E9154785C92F@gmail.com \
--to=okash.khawaja@gmail.com \
--cc=joe@perches.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peda@lysator.liu.se \
/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
all inboxes | Powered by JetHome®