From: Linus Walleij <linus.walleij@linaro.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: ext Tony Lindgren <tony@atomide.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: omap: drop omap_gpio_list
Date: Mon, 1 Oct 2018 13:24:11 +0200 [thread overview]
Message-ID: <CACRpkdb=+PDA1dz=Ui0OmhwKzDvCGEBMa7aUyqfg-s84gki1SA@mail.gmail.com> (raw)
In-Reply-To: <20180927233844.18443-1-grygorii.strashko@ti.com>
On Fri, Sep 28, 2018 at 1:38 AM Grygorii Strashko
<grygorii.strashko@ti.com> wrote:
> omap_gpio_list is unused so drop it.
>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Patch applied with Tony's ACK.
Yours,
Linus Walleij
prev parent reply other threads:[~2018-10-01 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 23:38 [PATCH] gpio: omap: drop omap_gpio_list Grygorii Strashko
2018-09-28 16:49 ` Tony Lindgren
2018-10-01 11:24 ` Linus Walleij [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='CACRpkdb=+PDA1dz=Ui0OmhwKzDvCGEBMa7aUyqfg-s84gki1SA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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).