From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Fox <fox.nicholas.j@gmail.com>
Cc: jonathankim@gctsemi.com, deanahn@gctsemi.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gdm724x: Rename variable for consistency
Date: Mon, 28 Aug 2017 10:43:10 +0200 [thread overview]
Message-ID: <20170828084310.GA9926@kroah.com> (raw)
In-Reply-To: <20170824231853.12007-1-fox.nicholas.j@gmail.com>
On Thu, Aug 24, 2017 at 07:18:53PM -0400, Nick Fox wrote:
> Rename dftEpsId variable to dft_eps_ID to be consistent with other
> variables in the source file.
>
> Signed-off-by: Nick Fox <fox.nicholas.j@gmail.com>
> ---
> drivers/staging/gdm724x/hci_packet.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Always test-build your patches, to not do so is rude to those of us you
expect to apply your patch :(
greg k-h
next prev parent reply other threads:[~2017-08-28 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 23:18 [PATCH] staging: gdm724x: Rename variable for consistency Nick Fox
2017-08-28 8:43 ` Greg KH [this message]
2017-08-30 3:11 ` [PATCH v2] staging : " Nick Fox
2017-08-31 16:27 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2017-08-31 16:47 [PATCH] staging: " Nick Fox
2017-09-01 6:58 ` Greg KH
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=20170828084310.GA9926@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=deanahn@gctsemi.com \
--cc=devel@driverdev.osuosl.org \
--cc=fox.nicholas.j@gmail.com \
--cc=jonathankim@gctsemi.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