Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ryder Lee <ryder.lee@mediatek.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Sean Wang <sean.wang@mediatek.com>, YF Luo <yf.luo@mediatek.com>,
	<linux-wireless@vger.kernel.org>,
	Yiwei Chung <yiwei.chung@mediatek.com>,
	<linux-mediatek@lists.infradead.org>, Roy Luo <royluo@google.com>,
	"Lorenzo Bianconi" <lorenzo.bianconi@redhat.com>,
	Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH 0/5] fix many checkpatch.pl warnings
Date: Wed, 24 Jul 2019 11:22:42 +0800	[thread overview]
Message-ID: <1563938562.9134.1.camel@mtkswgap22> (raw)
In-Reply-To: <8736ixrvhb.fsf@purkki.adurom.net>

On Tue, 2019-07-23 at 11:44 +0300, Kalle Valo wrote:
> Ryder Lee <ryder.lee@mediatek.com> writes:
> 
> > This gathers many subsets to fix checkpatch.pl warnings.
> 
> Thanks, this is much better now.
> 
> > I still keep some warnings there due to readability.
> > (The most of them are - networking block comments or 80 characters limit)
> 
> I do the same in ath10k. BTW, here's my simple script which I use to
> filter unwanted checkpatch warnings etc:
> 
> https://github.com/qca/qca-swiss-army-knife/blob/master/tools/scripts/ath10k/ath10k-check
> 

It's really useful!

Thanks
Ryder



      reply	other threads:[~2019-07-24  3:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  5:31 [PATCH 0/5] fix many checkpatch.pl warnings Ryder Lee
2019-07-22  5:31 ` [PATCH 1/5] mt76: Add paragraphs to describe the config symbols fully Ryder Lee
2019-07-22  5:31 ` [PATCH 2/5] mt76: mt7603: fix some checkpatch warnings Ryder Lee
2019-07-22  5:31 ` [PATCH 3/5] mt76: mt7615: " Ryder Lee
2019-07-22  5:31 ` [PATCH 4/5] mt76: mt76x02: " Ryder Lee
2019-07-22  5:31 ` [PATCH 5/5] mt76: " Ryder Lee
2019-07-23  8:44 ` [PATCH 0/5] fix many checkpatch.pl warnings Kalle Valo
2019-07-24  3:22   ` Ryder Lee [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=1563938562.9134.1.camel@mtkswgap22 \
    --to=ryder.lee@mediatek.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=nbd@nbd.name \
    --cc=royluo@google.com \
    --cc=sean.wang@mediatek.com \
    --cc=yf.luo@mediatek.com \
    --cc=yiwei.chung@mediatek.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