From: Greg KH <gregkh@linuxfoundation.org>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
outreachy@lists.linux.dev
Subject: Re: [PATCH v5 2/6] staging: vt6655: refactor code in s_uGetRTSCTSDuration
Date: Thu, 27 Oct 2022 11:19:32 +0200 [thread overview]
Message-ID: <Y1pNJMvl89jgq9qz@kroah.com> (raw)
In-Reply-To: <0e6a307052d3a354a850a502e509f46baccdbe1e.1666849707.git.tanjubrunostar0@gmail.com>
On Thu, Oct 27, 2022 at 08:59:04AM +0000, Tanjuate Brunostar wrote:
> refactor long lines of code in the function: s_uGetRTSCTSDuration
Please write full sentences.
Also please read the in-kernel documentation for how to write good
changelog text. Specifically look at the section entitled "The
canonical patch format" in the kernel file,
Documentation/SubmittingPatches for a description of how to do this
properly.
Do this for all of the patches in this series.
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-27 9:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 6:01 [PATCH v5 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c Tanjuate Brunostar
2022-10-28 6:34 ` Tanjuate Brunostar
2022-10-27 9:05 ` Tanjuate Brunostar
2022-10-27 8:59 ` Tanjuate Brunostar
2022-10-27 6:01 ` [PATCH v5 1/6] staging: vt6655: fix lines ending in a '(' Tanjuate Brunostar
2022-10-28 6:39 ` [PATCH v7 1/6] staging: vt6655: fix lines of code " Tanjuate Brunostar
2022-10-27 9:05 ` [PATCH v6 1/6] staging: vt6655: fix lines " Tanjuate Brunostar
2022-10-27 8:59 ` [PATCH v5 " Tanjuate Brunostar
2022-10-27 9:20 ` Greg KH
2022-10-28 5:55 ` [PATCH v6 " Philipp Hortmann
2022-10-28 14:57 ` [PATCH v7 1/6] staging: vt6655: fix lines of code " Philipp Hortmann
2022-10-28 16:42 ` Tanju Brunostar
2022-10-28 17:52 ` Alison Schofield
2022-10-28 17:59 ` Tanju Brunostar
2022-10-27 6:01 ` [PATCH v5 2/6] staging: vt6655: refactor code in s_uGetRTSCTSDuration Tanjuate Brunostar
2022-10-28 6:39 ` [PATCH v7 2/6] staging: vt6655: split code lines " Tanjuate Brunostar
2022-10-27 9:05 ` [PATCH v6 2/6] staging: vt6655: refactor code " Tanjuate Brunostar
2022-10-27 8:59 ` [PATCH v5 " Tanjuate Brunostar
2022-10-27 6:37 ` Greg KH
2022-10-27 9:19 ` Greg KH [this message]
2022-10-27 13:09 ` Tanju Brunostar
2022-10-27 14:50 ` Greg KH
2022-10-27 6:01 ` [PATCH v5 3/6] staging: vt6655: refactor code in s_uFillDataHead Tanjuate Brunostar
2022-10-28 6:39 ` [PATCH v7 3/6] staging: vt6655: split long lines of " Tanjuate Brunostar
2022-10-27 9:05 ` [PATCH v6 3/6] staging: vt6655: refactor " Tanjuate Brunostar
2022-10-27 8:59 ` [PATCH v5 " Tanjuate Brunostar
2022-10-27 6:01 ` [PATCH v5 4/6] staging: vt6655: refactor code in s_vGenerateTxParameter Tanjuate Brunostar
2022-10-28 6:39 ` [PATCH v7 4/6] staging: vt6655: split long lines of " Tanjuate Brunostar
2022-10-27 9:05 ` [PATCH v6 4/6] staging: vt6655: refactor " Tanjuate Brunostar
2022-10-27 8:59 ` [PATCH v5 " Tanjuate Brunostar
2022-10-27 6:01 ` [PATCH v5 5/6] staging: vt6655: refactor code in the rest of the file Tanjuate Brunostar
2022-10-28 6:39 ` [PATCH v7 5/6] staging: vt6655: split long lines of code in " Tanjuate Brunostar
2022-10-27 9:05 ` [PATCH v6 5/6] staging: vt6655: refactor code in the rest of " Tanjuate Brunostar
2022-10-27 8:59 ` [PATCH v5 " Tanjuate Brunostar
2022-10-27 6:01 ` [PATCH v5 6/6] staging: vt6655: refactor code to avoid a line ending in '(' Tanjuate Brunostar
2022-10-28 17:40 ` [PATCH v7 6/6] staging: vt6655: fix lines of code ending in a '(' Tanjuate Brunostar
2022-10-28 6:39 ` Tanjuate Brunostar
2022-10-27 9:05 ` [PATCH v6 6/6] staging: vt6655: refactor code to avoid a line ending in '(' Tanjuate Brunostar
2022-10-27 8:59 ` [PATCH v5 " Tanjuate Brunostar
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=Y1pNJMvl89jgq9qz@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=tanjubrunostar0@gmail.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 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.