From: Alexandre Courbot <gnurou@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: [PATCH] gpio: improve error reporting on own descriptors
Date: Mon, 8 Jun 2015 11:19:10 +0900 [thread overview]
Message-ID: <CAAVeFuJ9cOg-_RJpbDPvTmx8iT7e9n+QjArp6tj5ASeq27Naww@mail.gmail.com> (raw)
In-Reply-To: <1433496970-20392-1-git-send-email-linus.walleij@linaro.org>
On Fri, Jun 5, 2015 at 6:36 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> When requesting own descriptors through hogs, it is useful to
> get some details about what's going on if we encounter problems.
Acked-by: Alexandre Courbot <acourbot@nvidia.com>
Linus, I apologize for my inactivity lately - hopefully I will have
some more time to spend on GPIO reviews. Thanks for your patience!
prev parent reply other threads:[~2015-06-08 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 9:36 [PATCH] gpio: improve error reporting on own descriptors Linus Walleij
2015-06-08 2:19 ` Alexandre Courbot [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=CAAVeFuJ9cOg-_RJpbDPvTmx8iT7e9n+QjArp6tj5ASeq27Naww@mail.gmail.com \
--to=gnurou@gmail.com \
--cc=acourbot@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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).