From: Joe Perches <joe@perches.com>
To: Jignesh Patel <jigs0101@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Martin Kaiser <martin@kaiser.cx>,
Dan Carpenter <dan.carpenter@oracle.com>,
Ivan Safonov <insafonov@gmail.com>,
Paul McQuade <paulmcquad@gmail.com>,
Phillip Potter <phil@philpotter.co.uk>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8188eu: Line over 100 characters
Date: Thu, 22 Jul 2021 09:59:23 -0700 [thread overview]
Message-ID: <ff955d0fa6c50954d52ca93f0bee2e79627fe861.camel@perches.com> (raw)
In-Reply-To: <20210722164144.377781-1-jigs0101@gmail.com>
On Thu, 2021-07-22 at 22:11 +0530, Jignesh Patel wrote:
> Break various lines into multiple lines to respect 100 character width limit.
[]
> diff --git a/drivers/staging/rtl8188eu/core/rtw_ap.c b/drivers/staging/rtl8188eu/core/rtw_ap.c
[]
> @@ -254,9 +254,12 @@ void expire_timeout_chk(struct adapter *padapter)
> updated = ap_free_sta(padapter, psta, true,
> WLAN_REASON_DEAUTH_LEAVING);
> } else {
> - /* TODO: Aging mechanism to digest frames in sleep_q to avoid running out of xmitframe */
> + /** TODO: Aging mechanism to digest frames in
Please do not use double asterisks to start a comment.
next prev parent reply other threads:[~2021-07-23 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 16:41 [PATCH] staging: rtl8188eu: Line over 100 characters Jignesh Patel
2021-07-22 16:46 ` Greg Kroah-Hartman
2021-07-22 16:59 ` Joe Perches [this message]
2021-07-23 7:08 ` Jignesh Patel
2021-07-23 9:45 [PATCH] " Jignesh Patel
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=ff955d0fa6c50954d52ca93f0bee2e79627fe861.camel@perches.com \
--to=joe@perches.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=insafonov@gmail.com \
--cc=jigs0101@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux@roeck-us.net \
--cc=martin@kaiser.cx \
--cc=paulmcquad@gmail.com \
--cc=phil@philpotter.co.uk \
/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).