From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: 104-idio-16: Use lowercase symbol names for const variables
Date: Sun, 8 Nov 2015 20:28:35 -0500 [thread overview]
Message-ID: <563FF6C3.4000009@gmail.com> (raw)
In-Reply-To: <CAAVeFuJT7uxbQ_rf2o=6w4Ub3aW4Lhn_ED_JQZ+TNpORAVom8A@mail.gmail.com>
On 11/08/2015 06:53 PM, Alexandre Courbot wrote:
> Apart from that this patch seems harmless and the repositioning of
> some constant declarations is also welcome.
I'll create a separate patch to reposition the constant declarations. Where in
particular do you believe would be best for them to be positioned?
William Breathitt Gray
next prev parent reply other threads:[~2015-11-09 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 12:30 [PATCH] gpio: 104-idio-16: Use lowercase symbol names for const variables William Breathitt Gray
2015-11-08 23:53 ` Alexandre Courbot
2015-11-09 1:28 ` William Breathitt Gray [this message]
2015-11-09 6:09 ` Alexandre Courbot
2015-11-17 11:04 ` Linus Walleij
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=563FF6C3.4000009@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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).