All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-gpio <linux-gpio@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bamvor Jian Zhang <bamv2005@gmail.com>,
	Drew Fustini <drew@pdp7.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v5 4/7] gpiolib: add support for biasing output lines
Date: Tue, 5 Nov 2019 14:06:49 +0800	[thread overview]
Message-ID: <20191105060649.GA1302@sol> (raw)
In-Reply-To: <20191105020342.GA16739@sol>

On Tue, Nov 05, 2019 at 10:03:42AM +0800, Kent Gibson wrote:
> On Mon, Nov 04, 2019 at 05:19:14PM +0100, Bartosz Golaszewski wrote:
> > pon., 4 lis 2019 o 16:59 Kent Gibson <warthog618@gmail.com> napisał(a):
> > >
> > > > Ugh, I missed one thing here - my for-next branch doesn't contain the
> > > > following commit e735244e2cf0 ("gpiolib: don't clear FLAG_IS_OUT when
> > > > emulating open-drain/open-source") which happens to modify this
> > > > function.
> > > >
> > > > If I provided you with a branch containing it - would it be a lot of
> > > > effort on your part to rebase it on top of it? If so - I can do it
> > > > myself.
> > > >
> > >
> > > I can do a rebase - though not until tomorrow (it is getting late here).
> > > I would like that commit in as well - I suspect it being missing is
> > > the reason a couple of the gpiod tests I was working on are failing.
> > > I was in the process of tracking that down when I switched back to this.
> > >
> > > Cheers,
> > > Kent.
> > >
> > >
> > 
> > No problem, it can wait until tomorrow. Please use the following
> > branch - gpio/for-kent - from my tree.
> > 
> 
> That was a lot simpler than I expected - it rebased cleanly onto the 
> new branch.  And fixed the gpiod test errors I was trying to track down.
> Will submit v6 shortly.
> 

Maybe I'm missing something, but given that the rebase was clean, was 
there actually any need for v6?
i.e. anyone can rebase the v5 patch onto gpio/for-kent:

$ git checkout -b pud_rebase brgl/gpio/for-next
Branch 'pud_rebase' set up to track remote branch 'gpio/for-next' from 'brgl'.
Switched to a new branch 'pud_rebase'
$ git am PATCH-v5-0-7-gpio-expose-line-bias-flags-to-userspace.mbox
Applying: gpio: expose pull-up/pull-down line flags to userspace
Applying: gpiolib: add support for pull up/down to lineevent_create
Applying: gpiolib: add support for disabling line bias
Applying: gpiolib: add support for biasing output lines
Applying: gpio: mockup: add set_config to support pull up/down
Applying: gpiolib: move validation of line handle flags into helper function
Applying: gpio: add new SET_CONFIG ioctl() to gpio chardev
$ git rebase brgl/gpio/for-kent
First, rewinding head to replay your work on top of it...
Applying: gpio: expose pull-up/pull-down line flags to userspace
Applying: gpiolib: add support for pull up/down to lineevent_create
Applying: gpiolib: add support for disabling line bias
Applying: gpiolib: add support for biasing output lines
Using index info to reconstruct a base tree...
M	drivers/gpio/gpiolib.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpio/gpiolib.c
Applying: gpio: mockup: add set_config to support pull up/down
Applying: gpiolib: move validation of line handle flags into helper function
Applying: gpio: add new SET_CONFIG ioctl() to gpio chardev

Or was it more about eyeballing and retesting the rebase in case the
3-way merge went haywire?

Cheers,
Kent.

  reply	other threads:[~2019-11-05  6:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 15:38 [PATCH v5 0/7] gpio: expose line bias flags to userspace Kent Gibson
2019-11-04 15:38 ` [PATCH v5 1/7] gpio: expose pull-up/pull-down line " Kent Gibson
2019-11-04 15:38 ` [PATCH v5 2/7] gpiolib: add support for pull up/down to lineevent_create Kent Gibson
2019-11-04 15:38 ` [PATCH v5 3/7] gpiolib: add support for disabling line bias Kent Gibson
2019-11-04 15:38 ` [PATCH v5 4/7] gpiolib: add support for biasing output lines Kent Gibson
2019-11-04 15:50   ` Bartosz Golaszewski
2019-11-04 15:59     ` Kent Gibson
2019-11-04 16:19       ` Bartosz Golaszewski
2019-11-05  2:03         ` Kent Gibson
2019-11-05  6:06           ` Kent Gibson [this message]
2019-11-05  9:10             ` Bartosz Golaszewski
2019-11-04 15:38 ` [PATCH v5 5/7] gpio: mockup: add set_config to support pull up/down Kent Gibson
2019-11-04 15:38 ` [PATCH v5 6/7] gpiolib: move validation of line handle flags into helper function Kent Gibson
2019-11-04 15:38 ` [PATCH v5 7/7] gpio: add new SET_CONFIG ioctl() to gpio chardev Kent Gibson
2019-11-04 19:58 ` [PATCH v5 0/7] gpio: expose line bias flags to userspace Drew Fustini
2019-11-05  0:12   ` Kent Gibson
2019-11-05  5:34     ` Kent Gibson

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=20191105060649.GA1302@sol \
    --to=warthog618@gmail.com \
    --cc=bamv2005@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=drew@pdp7.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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 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.