From: Greg KH <gregkh@linuxfoundation.org>
To: "Javier F. Arias" <jarias.linux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] staging: rtl8723bs: Rename variable
Date: Wed, 13 Nov 2019 11:45:15 +0100 [thread overview]
Message-ID: <20191113104515.GC2068945@kroah.com> (raw)
In-Reply-To: <1610b265f1c6ee0148002642836283fb3757a36f.1573605920.git.jarias.linux@gmail.com>
On Tue, Nov 12, 2019 at 08:38:47PM -0500, Javier F. Arias wrote:
> This patch renames a variable name previously defined in uppercase.
That says what you did, but not _why_ you want to do it.
prev parent reply other threads:[~2019-11-13 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 1:34 [PATCH v2 1/4] staging: rtl8723bs: Add necessary braces Javier F. Arias
2019-11-13 1:36 ` [PATCH v2 2/4] staging: rtl8723bs: Fix unbalanced braces Javier F. Arias
2019-11-13 10:43 ` [Outreachy kernel] " Greg KH
2019-11-13 1:36 ` [PATCH v2 3/4] staging: rtl8723bs: Remove unnecessary conditional block Javier F. Arias
2019-11-13 10:44 ` Greg KH
2019-11-13 1:38 ` [PATCH v2 4/4] staging: rtl8723bs: Rename variable Javier F. Arias
2019-11-13 10:45 ` Greg KH [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=20191113104515.GC2068945@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jarias.linux@gmail.com \
--cc=linux-kernel@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 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).