From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nishad Kamdar <nishadkamdar@gmail.com>
Cc: devel@driverdev.osuosl.org, "Leonardo Brás" <leobras.c@gmail.com>,
linux-fbdev@vger.kernel.org, YueHaibing <yuehaibing@huawei.com>,
"Jani Nikula" <jani.nikula@intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Felix Siegel" <felix.siegel@stud.uni-hannover.de>,
"Matthias Wolf" <der_wolf_@web.de>,
linux-kernel@vger.kernel.org,
"Mamta Shukla" <mamtashukla555@gmail.com>,
"Radek Dostál" <radek.dostal@streamunlimited.com>,
"Renato Soma" <renatoys08@gmail.com>,
dri-devel@lists.freedesktop.org,
"Tim Cofala" <cofala@stud.uni-hannover.de>,
"Lee Jones" <lee.jones@linaro.org>
Subject: Re: [PATCH v2] Staging: fbtft: Switch to the gpio descriptor interface
Date: Tue, 15 Jan 2019 16:02:31 +0100 [thread overview]
Message-ID: <20190115150231.GA3418@kroah.com> (raw)
In-Reply-To: <20190115044704.GA20989@nishad>
On Tue, Jan 15, 2019 at 10:17:09AM +0530, Nishad Kamdar wrote:
> This switches the fbtft driver to use GPIO descriptors
> rather than numerical gpios:
>
> Utilize the GPIO library's intrinsic handling of OF GPIOs
> and polarity. If the line is flagged active low, gpiolib
> will deal with this.
>
> Remove gpios from platform device structure. Neither assign
> statically numbers to gpios in platform device nor allow
> gpios to be parsed as module parameters.
>
> Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> Changes in v2:
> - Merge all patches in a single patch. This is because the
> first patch changes par->gpio from an int to a pointer
> so all the checks have to be updated in the same patch.
> Otherwie it breaks 'git bisect'.
The "v2" information goes below the --- line please.
Also, I got 2 copies of this, both different, so I have no idea which to
apply. Please fix up and resend a v3.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-15 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 4:47 [PATCH v2] Staging: fbtft: Switch to the gpio descriptor interface Nishad Kamdar
2019-01-15 15:02 ` Greg Kroah-Hartman [this message]
2019-01-16 17:14 ` Nishad Kamdar
-- strict thread matches above, loose matches on Subject: below --
2018-12-04 16:51 Nishad Kamdar
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=20190115150231.GA3418@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cofala@stud.uni-hannover.de \
--cc=daniel.vetter@ffwll.ch \
--cc=der_wolf_@web.de \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.siegel@stud.uni-hannover.de \
--cc=jani.nikula@intel.com \
--cc=lee.jones@linaro.org \
--cc=leobras.c@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mamtashukla555@gmail.com \
--cc=nishadkamdar@gmail.com \
--cc=radek.dostal@streamunlimited.com \
--cc=renatoys08@gmail.com \
--cc=yuehaibing@huawei.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