From: Kalle Valo <kvalo@codeaurora.org>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: Pkshih <pkshih@realtek.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
莊彥宣 <yhchuang@realtek.com>,
"Johannes Berg" <johannes.berg@intel.com>,
"Souptick Joarder" <jrdr.linux@gmail.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: Re: Two rtlwifi drivers?
Date: Mon, 16 Oct 2017 16:07:47 +0300 [thread overview]
Message-ID: <87fuajmeak.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <ed361ae7-864e-1179-c7da-3ff10f4c73e2@rempel-privat.de> (Oleksij Rempel's message of "Mon, 16 Oct 2017 08:46:10 +0200")
Oleksij Rempel <linux@rempel-privat.de> writes:
>> 4) As Kalle mentioned, rtlwifi contains many magic numbers, and I
>> plan to fix them after rtl8723de and rtl8821ce. Because the drivers
>> are developing, the changes will make us hard to integrate. However,
>> I don't have plan to process the magic numbers in the module phydm,
>> because the most of BB/RF registers contain many functions. And
>> it doesn't have a register name but a bit field name instead.
>> Our BB team guys say the use of enumeration or defined name will
>> be unreadable, and the name is meaningless for most people.
>
> Experience with ath9k driver showed, that development was kind of
> balanced between two groups, QCA and Community (Other companies,
> researches, education and so on.). Saying: "you will not understand it
> any way" is nor really helpful :)
> Please don't repeat bad experience of Broadcom.
I agree with Oleksij here, but I want to still point out that there are
cases when using magic numbers are ok, for example look at
ar5008_initvals.h from ath9k. So it depends on case by case.
--
Kalle Valo
next prev parent reply other threads:[~2017-10-16 13:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 10:08 [PATCH] staging: rtlwifi: check for array overflow Dan Carpenter
2017-08-24 12:14 ` Two rtlwifi drivers? Kalle Valo
2017-08-24 14:41 ` Larry Finger
2017-10-11 9:06 ` Kalle Valo
2017-10-11 13:13 ` Greg Kroah-Hartman
2017-10-11 13:54 ` Dan Carpenter
2017-10-11 14:19 ` Larry Finger
2017-10-12 8:57 ` Kalle Valo
2017-10-12 8:38 ` Kalle Valo
2017-10-12 10:34 ` Greg Kroah-Hartman
2017-10-16 2:41 ` Pkshih
2017-10-16 6:46 ` Oleksij Rempel
2017-10-16 13:07 ` Kalle Valo [this message]
2017-10-16 13:11 ` Oleksij Rempel
2017-10-16 7:45 ` Dan Carpenter
2017-10-16 13:03 ` Kalle Valo
2017-10-16 7:50 ` Greg Kroah-Hartman
2017-10-17 1:24 ` Pkshih
2017-10-16 13:22 ` Kalle Valo
2017-10-17 1:45 ` Pkshih
2017-10-18 5:33 ` Kalle Valo
2017-08-24 18:51 ` [PATCH] staging: rtlwifi: check for array overflow Larry Finger
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=87fuajmeak.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=jrdr.linux@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=pkshih@realtek.com \
--cc=yhchuang@realtek.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).