From: Joe Perches <joe@perches.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-wireless@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: Re: [PATCH 1/1] New driver: rtl8723au (mac80211)
Date: Mon, 09 Mar 2015 12:07:37 -0700 [thread overview]
Message-ID: <1425928057.5428.53.camel@perches.com> (raw)
In-Reply-To: <wrfjtwxuouyx.fsf@ultrasam.lan.trained-monkey.org>
On Mon, 2015-03-09 at 15:02 -0400, Jes Sorensen wrote:
> Joe Perches <joe@perches.com> writes:
> > On Mon, 2015-03-09 at 14:43 -0400, Jes Sorensen wrote:
> >> Joe Perches <joe@perches.com> writes:
> >> > On Mon, 2015-03-09 at 13:00 -0400, Jes.Sorensen@redhat.com wrote:
> >> >> This is an alternate driver for the Realtek 8723AU (rtl8723au) written
> >> >> from scratch utilizing the mac80211 stack.
> >> >
> >> > Mostly trivial comments:
> >> >
> >> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> > []
> >> >> +RTL8XXXU WIRELESS DRIVER (rtl8xxxu)
> >> >> +M: Jes Sorensen <Jes.Sorensen@redhat.com>
> >> >> +L: linux-wireless@vger.kernel.org
> >> >> +W: http://intellinuxwireless.org
> >> >> +T: git git://git.Mkernel.org/pub/scm/linux/kernel/git/jes/linux.git
> >> >> + git branch rtl8723au-mac80211
> >> >
> >> > please keep this on one line
> >>
> >> Lines are 80 characters, and it won't fit.
> >
> > For code yes, for MAINTAINERS no.
> > There are many lines > 80 chars there.
> > Please keep:
> > <TYPE>: entry
> > on single lines.
>
> Longer than 80 characters is ugly and you haven't provided any
> justification for putting it on one line.
<TYPE>: entries are single line.
> >> >> +struct rtl8xxxu_priv {
> >> > []
> >> >> + u32 has_wifi:1;
> >> >> + u32 has_bluetooth:1;
> >> >> + u32 enable_bluetooth:1;
> >> >> + u32 has_gps:1;
> >> >> + u32 vendor_umc:1;
> >> >> + u32 has_polarity_ctrl:1;
> >> >> + u32 has_eeprom:1;
> >> >> + u32 boot_eeprom:1;
> >> >> + u32 ep_tx_high_queue:1;
> >> >> + u32 ep_tx_normal_queue:1;
> >> >> + u32 ep_tx_low_queue:1;
> >> >> + u32 path_a_hi_power:1;
> >> >
> >> > These might be better as bool instead of packed bitfields.
> >>
> >> bool wastes 4 bytes in the struct, so no that would be worse.
> >
> > It's a used-once struct. 4 bytes, wow.
>
> Once per device - but it all comes down to a matter of style and taste
> of the developer in the end. You seem to be obsessed with imposing your
> ideas on everybody, rather than actually looking for real bugs.
I'm not imposing anything.
You can accept it or not.
btw: every use of any bitfield requires more code
for RMW than a byte access does.
next prev parent reply other threads:[~2015-03-09 19:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 17:00 [PATCH v2 0/1] New driver: rtl8723au (mac80211) Jes.Sorensen
2015-03-09 17:00 ` [PATCH 1/1] " Jes.Sorensen
2015-03-09 17:46 ` Johannes Berg
2015-03-09 18:35 ` Jes Sorensen
2015-03-09 19:52 ` Johannes Berg
2015-03-09 18:20 ` Joe Perches
2015-03-09 18:43 ` Jes Sorensen
2015-03-09 18:51 ` Joe Perches
2015-03-09 19:02 ` Jes Sorensen
2015-03-09 19:07 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-05 20:04 Xose Vazquez Perez
2015-05-05 21:40 ` Jes Sorensen
2015-05-07 9:43 ` Xose Vazquez Perez
2015-05-07 15:43 ` Larry Finger
2015-03-23 20:24 [PATCH v3 0/1] " Jes.Sorensen
2015-03-23 20:25 ` [PATCH 1/1] " Jes.Sorensen
2015-03-23 22:51 ` Joe Perches
2015-03-24 1:25 ` Jes Sorensen
2015-04-28 8:37 ` Kalle Valo
2015-04-28 12:55 ` Kalle Valo
2015-04-28 14:27 ` Jes Sorensen
2015-04-28 15:15 ` Larry Finger
2015-09-06 13:38 ` Kalle Valo
2015-09-06 16:41 ` Larry Finger
2015-09-07 13:37 ` Kalle Valo
2015-09-07 18:43 ` Jes Sorensen
2015-09-07 18:50 ` Larry Finger
2015-09-09 14:16 ` Jes Sorensen
2015-09-29 8:56 ` Kalle Valo
2015-09-29 10:42 ` Jes Sorensen
2015-03-06 22:15 [PATCH 0/1] " Jes.Sorensen
2015-03-06 22:15 ` [PATCH 1/1] " Jes.Sorensen
2015-03-06 22:59 ` Joe Perches
2015-03-07 5:18 ` Jes Sorensen
2015-03-07 5:23 ` Joe Perches
2015-03-07 5:33 ` Jes Sorensen
2015-03-07 21:30 ` Larry Finger
2015-03-09 17:08 ` Jes Sorensen
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=1425928057.5428.53.camel@perches.com \
--to=joe@perches.com \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.