From: Richard Cochran <richardcochran@gmail.com>
To: Michael van der Westhuizen <michael@smart-africa.com>
Cc: linux-arm-kernel@lists.infradead.org,
Alexandre Courbot <gnurou@gmail.com>,
devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, Alan Tull <atull@altera.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Dinh Nguyen <dinguyen@altera.com>
Subject: Re: [PATCH 1/2] gpio: dwapb: Use human understandable gpio numbering.
Date: Fri, 3 Jul 2015 11:13:47 +0200 [thread overview]
Message-ID: <20150703091347.GA17808@localhost.localdomain> (raw)
In-Reply-To: <267A46E7-C5C5-4696-90CC-D44F4130B3EF@smart-africa.com>
On Thu, Jul 02, 2015 at 08:05:26AM +0100, Michael van der Westhuizen wrote:
> > On 01 Jul 2015, at 8:34 PM, Richard Cochran <richardcochran@gmail.com> wrote:
> >
> > The system-on-chips using this IP core have well defined gpio numbers.
> > Instead of using random numbers, this patch lets the device tree specify
> > the correct gpio numbering.
>
> The subject should not end with a full-stop.
Sorry, I really have no idea what you mean.
Thanks,
Richard
next prev parent reply other threads:[~2015-07-03 9:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 19:34 [PATCH 0/2] gpio: dwapb: allow sane gpio numbering Richard Cochran
2015-07-01 19:34 ` [PATCH 1/2] gpio: dwapb: Use human understandable " Richard Cochran
2015-07-02 7:05 ` Michael van der Westhuizen
2015-07-02 14:20 ` Richard Cochran
[not found] ` <20150702142058.GA9349-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-07-16 7:57 ` Linus Walleij
2015-07-16 8:18 ` Michael van der Westhuizen
2015-07-16 18:19 ` Richard Cochran
2015-07-03 9:13 ` Richard Cochran [this message]
2015-07-03 9:18 ` Michael van der Westhuizen
[not found] ` <C1BD6DA3-F32E-4CAD-8DA9-6F74A7966DBE-XrNoQAPr3WXM9gW82pYGhQ@public.gmane.org>
2015-07-03 10:36 ` Richard Cochran
2015-07-03 10:55 ` Russell King - ARM Linux
2015-07-16 7:52 ` Linus Walleij
2015-07-16 8:16 ` Michael van der Westhuizen
2015-07-02 7:36 ` Sebastian Andrzej Siewior
2015-07-02 14:26 ` Richard Cochran
2015-07-02 14:30 ` Sebastian Andrzej Siewior
[not found] ` <55954B17.3020303-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2015-07-02 15:21 ` Richard Cochran
[not found] ` <20150702152147.GA10111-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-07-02 15:54 ` Sebastian Andrzej Siewior
2015-07-02 16:02 ` Michael van der Westhuizen
2015-07-03 13:30 ` Michael van der Westhuizen
[not found] ` <d6b5ce85a17164970d454583560e07f7aed7b8ca.1435777856.git.rcochran-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2015-07-16 7:50 ` Linus Walleij
2015-07-16 17:10 ` Richard Cochran
2015-07-16 17:19 ` Richard Cochran
2015-07-27 10:19 ` Linus Walleij
2015-07-27 11:28 ` Richard Cochran
2015-07-27 12:26 ` Sebastian Andrzej Siewior
[not found] ` <cover.1435777856.git.rcochran-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2015-07-01 19:34 ` [PATCH 2/2] arm: dts: socfpga: Provide the gpio numbers in the controller nodes Richard Cochran
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=20150703091347.GA17808@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=atull@altera.com \
--cc=bigeasy@linutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@altera.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=michael@smart-africa.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 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).