From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: Two rtlwifi drivers?
Date: Mon, 16 Oct 2017 08:07:07 +0000 [thread overview]
Message-ID: <59E468AB.7010402@bfs.de> (raw)
In-Reply-To: <87h8wxw4bq.fsf@kamboji.qca.qualcomm.com>
Hello,
just a general remark:
The discussion is useful to improve the code quality in the kernel.
NTL i doubt that it belongs to the kernel-janitors list.
please remove kernel-janitors from CC before posting.
thx for doing so.
re,
wh
Am 16.10.2017 09:45, schrieb Dan Carpenter:
> On Mon, Oct 16, 2017 at 02:41:38AM +0000, Pkshih wrote:
>> 2) The rtlwifi in staging
>> In staging, the module phydm v13 contains bugs, so I want to upgrade
>> to v21 (Realtek internal version number). This upgrade contains a
>> big patch that the difference between v13 and v21, and there are
>> 40+ patches to support this upgrade. I have three options, and
>> I want to know which one is prefer.
>
> We can't discuss patches we haven't seend. Please just send them right
> away without any delay to both lists, and we can decide from there.
>
> 40 patches is a medium size set, patch that we are used to dealing with
> every day.
>
> regards,
> dan carpenter
>
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-10-16 8:07 UTC|newest]
Thread overview: 42+ 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 10:08 ` Dan Carpenter
2017-08-24 12:14 ` Two rtlwifi drivers? Kalle Valo
2017-08-24 12:14 ` Kalle Valo
2017-08-24 14:41 ` Larry Finger
2017-08-24 14:41 ` Larry Finger
2017-10-11 9:06 ` Kalle Valo
2017-10-11 9:06 ` Kalle Valo
2017-10-11 13:13 ` Greg Kroah-Hartman
2017-10-11 13:13 ` Greg Kroah-Hartman
2017-10-11 13:54 ` Dan Carpenter
2017-10-11 13:54 ` Dan Carpenter
2017-10-11 14:19 ` Larry Finger
2017-10-11 14:19 ` Larry Finger
2017-10-12 8:57 ` Kalle Valo
2017-10-12 8:57 ` Kalle Valo
2017-10-12 8:38 ` Kalle Valo
2017-10-12 8:38 ` Kalle Valo
2017-10-12 10:34 ` Greg Kroah-Hartman
2017-10-12 10:34 ` Greg Kroah-Hartman
2017-10-16 2:41 ` Pkshih
2017-10-16 2:41 ` Pkshih
2017-10-16 6:46 ` Oleksij Rempel
2017-10-16 6:46 ` Oleksij Rempel
2017-10-16 13:07 ` Kalle Valo
2017-10-16 13:07 ` Kalle Valo
2017-10-16 13:11 ` Oleksij Rempel
2017-10-16 13:11 ` Oleksij Rempel
2017-10-16 7:45 ` Dan Carpenter
2017-10-16 7:45 ` Dan Carpenter
2017-10-16 13:03 ` Kalle Valo
2017-10-16 13:03 ` Kalle Valo
2017-10-16 7:50 ` Greg Kroah-Hartman
2017-10-16 7:50 ` Greg Kroah-Hartman
2017-10-17 1:24 ` Pkshih
2017-10-16 13:22 ` Kalle Valo
2017-10-16 13:22 ` Kalle Valo
2017-10-17 1:45 ` Pkshih
2017-10-18 5:33 ` Kalle Valo
2017-10-16 8:07 ` walter harms [this message]
2017-08-24 18:51 ` [PATCH] staging: rtlwifi: check for array overflow Larry Finger
2017-08-24 18:51 ` 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=59E468AB.7010402@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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.