From: Kent Gibson <warthog618@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v3] gpiolib: split character device into gpiolib-cdev
Date: Tue, 16 Jun 2020 17:40:17 +0800 [thread overview]
Message-ID: <20200616094017.GA5118@sol> (raw)
In-Reply-To: <CACRpkdZ9to8LRMFiGNW5gd-v901j2AsKDWKojw=f4dRaJSm4kQ@mail.gmail.com>
On Tue, Jun 16, 2020 at 10:37:32AM +0200, Linus Walleij wrote:
> On Wed, Jun 10, 2020 at 1:52 AM Kent Gibson <warthog618@gmail.com> wrote:
>
> > Split the cdev specific functionality out of gpiolib.c and into
> > gpiolib-cdev.c. This improves the readability and maintainability of both
> > the cdev and core gpiolib code.
> >
> > Suggested-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > Signed-off-by: Kent Gibson <warthog618@gmail.com>
> >
> > ---
> >
> > Changes in v3:
> > - updated the gpiolib-cdev.c file comment.
> > - rebased to latest gpio/devel (no changes impacted this patch)
> > - dropped the patch commentary as the points mentioned are mostly
> > resolved - there still remain a couple of commits in gpio/fixes that will
> > conflict...
>
> I rebased my GPIO tree on v5.8-rc1 and the old version of the patch did
> not apply and neither did this, could you rebase this patch so I can
> apply it? Sorry for the moving target, the merge window times are
> a bit bumpy. :/
>
No problem - I was expecting a rebase to be in that patch's future from
the beginning.
Give v4 a try.
Cheers,
Kent.
prev parent reply other threads:[~2020-06-16 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 23:51 [PATCH v3] gpiolib: split character device into gpiolib-cdev Kent Gibson
2020-06-16 8:37 ` Linus Walleij
2020-06-16 9:40 ` Kent Gibson [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=20200616094017.GA5118@sol \
--to=warthog618@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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.