From: Vaibhav Gupta <vaibhavgupta40@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v1] gpio: Extend TODO to cover code duplication avoidance
Date: Fri, 3 Apr 2020 01:47:52 +0530 [thread overview]
Message-ID: <CAP+cEONqu_4ebwcE1VmrR8yfYzX-vp-rdZC8m_h8NBnugzG_eQ@mail.gmail.com> (raw)
In-Reply-To: <20200402200955.GD1922688@smile.fi.intel.com>
> I guess this answers the question in the previous thread.
> To be clear, scrap your patch and don't touch just gpio-ml-ioh alone.
> Basically it should be one patch to get rid the driver.
Sure! Will work on it.
-- Vaibhav Gupta
>
> JFYI, I will send couple of clean ups against gpio-pch.
next prev parent reply other threads:[~2020-04-02 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 19:21 [PATCH v1] gpio: Extend TODO to cover code duplication avoidance Andy Shevchenko
2020-04-02 19:35 ` Vaibhav Gupta
2020-04-02 20:09 ` Andy Shevchenko
2020-04-02 20:17 ` Vaibhav Gupta [this message]
2020-04-06 7:17 ` Bartosz Golaszewski
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=CAP+cEONqu_4ebwcE1VmrR8yfYzX-vp-rdZC8m_h8NBnugzG_eQ@mail.gmail.com \
--to=vaibhavgupta40@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.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).