All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishad Kamdar <nishadkamdar@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 04/26] Staging: fbtft: flexfb: Switch to the gpio descriptor interface
Date: Tue, 04 Dec 2018 15:56:54 +0000	[thread overview]
Message-ID: <20181204155634.GA16146@nishad> (raw)
In-Reply-To: <20181126101308.GI3088@unbuntlaptop>

On Mon, Nov 26, 2018 at 01:13:08PM +0300, Dan Carpenter wrote:
> On Sun, Nov 25, 2018 at 04:56:29PM +0530, Nishad Kamdar wrote:
> > This switches the flexfb.c to use GPIO descriptors
> > rather than numerical gpios.
> > 
> > Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> > ---
> >  drivers/staging/fbtft/flexfb.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/staging/fbtft/flexfb.c b/drivers/staging/fbtft/flexfb.c
> > index 2af474469e7d..c5fa59105a43 100644
> > --- a/drivers/staging/fbtft/flexfb.c
> > +++ b/drivers/staging/fbtft/flexfb.c
> > @@ -9,7 +9,7 @@
> >  #include <linux/kernel.h>
> >  #include <linux/init.h>
> >  #include <linux/vmalloc.h>
> > -#include <linux/gpio.h>
> > +#include <linux/gpio/consumer.h>
> >  #include <linux/spi/spi.h>
> >  #include <linux/delay.h>
> >  
> > @@ -521,7 +521,7 @@ static int flexfb_verify_gpios_dc(struct fbtft_par *par)
> >  {
> >  	fbtft_par_dbg(DEBUG_VERIFY_GPIOS, par, "%s()\n", __func__);
> >  
> > -	if (par->gpio.dc < 0) {
> > +	if (!par->gpio.dc) {
> >  		dev_err(par->info->device,
> >  			"Missing info about 'dc' gpio. Aborting.\n");
> >  		return -EINVAL;
> 
> We changed par->gpio.c from an int to a pointer in patch 1 so we have
> to update all the checks as well in the same patch.  Otherwise it breaks
> `git bisect`.
> 
> (I don't know this code well.  But it just feels like it has to be
> breaking git bisect just from from glancing at the patches.  Perhaps I
> have misunderstood).
> 
> regards,
> dan carpenter
> 
Ok. I'll merge them into one patch.

Thanks for the review and the pointer.

Regards,
Nishad

WARNING: multiple messages have this Message-ID (diff)
From: Nishad Kamdar <nishadkamdar@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 04/26] Staging: fbtft: flexfb: Switch to the gpio descriptor interface
Date: Tue, 4 Dec 2018 21:26:35 +0530	[thread overview]
Message-ID: <20181204155634.GA16146@nishad> (raw)
In-Reply-To: <20181126101308.GI3088@unbuntlaptop>

On Mon, Nov 26, 2018 at 01:13:08PM +0300, Dan Carpenter wrote:
> On Sun, Nov 25, 2018 at 04:56:29PM +0530, Nishad Kamdar wrote:
> > This switches the flexfb.c to use GPIO descriptors
> > rather than numerical gpios.
> > 
> > Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> > ---
> >  drivers/staging/fbtft/flexfb.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/staging/fbtft/flexfb.c b/drivers/staging/fbtft/flexfb.c
> > index 2af474469e7d..c5fa59105a43 100644
> > --- a/drivers/staging/fbtft/flexfb.c
> > +++ b/drivers/staging/fbtft/flexfb.c
> > @@ -9,7 +9,7 @@
> >  #include <linux/kernel.h>
> >  #include <linux/init.h>
> >  #include <linux/vmalloc.h>
> > -#include <linux/gpio.h>
> > +#include <linux/gpio/consumer.h>
> >  #include <linux/spi/spi.h>
> >  #include <linux/delay.h>
> >  
> > @@ -521,7 +521,7 @@ static int flexfb_verify_gpios_dc(struct fbtft_par *par)
> >  {
> >  	fbtft_par_dbg(DEBUG_VERIFY_GPIOS, par, "%s()\n", __func__);
> >  
> > -	if (par->gpio.dc < 0) {
> > +	if (!par->gpio.dc) {
> >  		dev_err(par->info->device,
> >  			"Missing info about 'dc' gpio. Aborting.\n");
> >  		return -EINVAL;
> 
> We changed par->gpio.c from an int to a pointer in patch 1 so we have
> to update all the checks as well in the same patch.  Otherwise it breaks
> `git bisect`.
> 
> (I don't know this code well.  But it just feels like it has to be
> breaking git bisect just from from glancing at the patches.  Perhaps I
> have misunderstood).
> 
> regards,
> dan carpenter
> 
Ok. I'll merge them into one patch.

Thanks for the review and the pointer.

Regards,
Nishad

  reply	other threads:[~2018-12-04 15:56 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 11:20 [PATCH 00/26] Staging: fbtft: Switch to the gpio descriptor interface Nishad Kamdar
2018-11-25 11:32 ` Nishad Kamdar
2018-11-25 11:23 ` [PATCH 01/26] Staging: fbtft: fbtft-core: " Nishad Kamdar
2018-11-25 11:35   ` Nishad Kamdar
2018-11-25 16:12   ` kbuild test robot
2018-11-25 16:12     ` kbuild test robot
2018-11-25 16:12     ` kbuild test robot
2018-11-25 11:24 ` [PATCH 02/26] Staging: fbtft: fbtft-bus: " Nishad Kamdar
2018-11-25 11:36   ` Nishad Kamdar
2018-11-25 11:24   ` Nishad Kamdar
2018-11-25 11:25 ` [PATCH 03/26] Staging: fbtft: fbtft-io: " Nishad Kamdar
2018-11-25 11:37   ` Nishad Kamdar
2018-11-25 11:26 ` [PATCH 04/26] Staging: fbtft: flexfb: " Nishad Kamdar
2018-11-25 11:38   ` Nishad Kamdar
2018-11-26 10:13   ` Dan Carpenter
2018-11-26 10:13     ` Dan Carpenter
2018-12-04 15:56     ` Nishad Kamdar [this message]
2018-12-04 15:56       ` Nishad Kamdar
2018-11-25 11:27 ` [PATCH 05/26] Staging: fbtft: fbtft-device: " Nishad Kamdar
2018-11-25 11:39   ` Nishad Kamdar
2018-11-25 11:28 ` [PATCH 06/26] Staging: fbtft: fb_upd161704: " Nishad Kamdar
2018-11-25 11:40   ` Nishad Kamdar
2018-11-25 11:29 ` [PATCH 07/26] Staging: fbtft: fb_sh1106: " Nishad Kamdar
2018-11-25 11:41   ` Nishad Kamdar
2018-11-25 11:29 ` [PATCH 08/26] Staging: fbtft: fb_uc1611: " Nishad Kamdar
2018-11-25 11:41   ` Nishad Kamdar
2018-11-25 11:30 ` [PATCH 09/26] Staging: fbtft: fb_s6d1211: " Nishad Kamdar
2018-11-25 11:42   ` Nishad Kamdar
2018-11-25 11:31 ` [PATCH 10/26] Staging: fbtft: fb_ili9320: " Nishad Kamdar
2018-11-25 11:43   ` Nishad Kamdar
2018-11-25 11:32 ` [PATCH 11/26] Staging: fbtft: fb_ili9340: " Nishad Kamdar
2018-11-25 11:44   ` Nishad Kamdar
2018-11-25 11:34 ` [PATCH 12/26] Staging: fbtft: fb_ssd1325: " Nishad Kamdar
2018-11-25 11:46   ` Nishad Kamdar
2018-11-25 11:35 ` [PATCH 13/26] Staging: fbtft: fb_ili9325: " Nishad Kamdar
2018-11-25 11:47   ` Nishad Kamdar
2018-11-25 11:35 ` [PATCH 14/26] Staging: fbtft: fb_ssd1289: " Nishad Kamdar
2018-11-25 11:47   ` Nishad Kamdar
2018-11-25 11:36 ` [PATCH 15/26] Staging: fbtft: fb_ssd1351: " Nishad Kamdar
2018-11-25 11:48   ` Nishad Kamdar
2018-11-25 11:37 ` [PATCH 16/26] Staging: fbtft: fb_uc1701: " Nishad Kamdar
2018-11-25 11:49   ` Nishad Kamdar
2018-11-25 11:37   ` Nishad Kamdar
2018-11-25 11:37 ` [PATCH 17/26] Staging: fbtft: fb_ssd1306: " Nishad Kamdar
2018-11-25 11:49   ` Nishad Kamdar
2018-11-25 11:38 ` [PATCH 18/26] Staging: fbtft: fb_bd663474: " Nishad Kamdar
2018-11-25 11:50   ` Nishad Kamdar
2018-11-25 11:38   ` Nishad Kamdar
2018-11-25 11:39 ` [PATCH 19/26] Staging: fbtft: fb_ssd1331: " Nishad Kamdar
2018-11-25 11:51   ` Nishad Kamdar
2018-11-25 11:39 ` [PATCH 20/26] Staging: fbtft: fb_ili9163: " Nishad Kamdar
2018-11-25 11:51   ` Nishad Kamdar
2018-11-25 11:40 ` [PATCH 21/26] Staging: fbtft: fb_agm1264k-fl: " Nishad Kamdar
2018-11-25 11:52   ` Nishad Kamdar
2018-11-25 11:41 ` [PATCH 22/26] Staging: fbtft: fb_pcd8544: " Nishad Kamdar
2018-11-25 11:53   ` Nishad Kamdar
2018-11-25 11:41   ` Nishad Kamdar
2018-11-25 11:42 ` [PATCH 23/26] Staging: fbtft: fb_ssd1305: " Nishad Kamdar
2018-11-25 11:54   ` Nishad Kamdar
2018-11-25 11:42   ` Nishad Kamdar
2018-11-25 11:43 ` [PATCH 24/26] Staging: fbtft: fb_tls8204: " Nishad Kamdar
2018-11-25 11:55   ` Nishad Kamdar
2018-11-25 11:43 ` [PATCH 25/26] Staging: fbtft: fb_watterott: " Nishad Kamdar
2018-11-25 11:55   ` Nishad Kamdar
2018-11-25 11:44 ` [PATCH 26/26] Staging: fbtft: fb_ra8875: " Nishad Kamdar
2018-11-25 11:56   ` 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=20181204155634.GA16146@nishad \
    --to=nishadkamdar@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.