From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Bamvor Jian Zhang <bamv2005@gmail.com>
Subject: Re: [PATCH v2 0/7] selftests: gpio: rework and port to GPIO uAPI v2
Date: Tue, 19 Jan 2021 19:21:09 +0800 [thread overview]
Message-ID: <20210119112109.GA23328@sol> (raw)
In-Reply-To: <CAMpxmJWMQ2uVJ77MYPr3dhy0=-P8FtAfz3BSoKbxh33J0Gx=Ug@mail.gmail.com>
On Tue, Jan 19, 2021 at 12:02:13PM +0100, Bartosz Golaszewski wrote:
> On Tue, Jan 19, 2021 at 11:59 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > On Tue, Jan 19, 2021 at 11:37:46AM +0100, Bartosz Golaszewski wrote:
> > > On Tue, Jan 19, 2021 at 1:35 AM Kent Gibson <warthog618@gmail.com> wrote:
> > > >
> > > > On Mon, Jan 18, 2021 at 04:04:51PM +0100, Linus Walleij wrote:
> > > > > On Thu, Jan 7, 2021 at 3:58 AM Kent Gibson <warthog618@gmail.com> wrote:
> > > > >
> > > > > > selftests: gpio: rework and simplify test implementation
> > > > > > selftests: gpio: remove obsolete gpio-mockup-chardev.c
> > > > > > selftests: remove obsolete build restriction for gpio
> > > > > > selftests: remove obsolete gpio references from kselftest_deps.sh
> > > > > > tools: gpio: remove uAPI v1 code no longer used by selftests
> > > > > > selftests: gpio: port to GPIO uAPI v2
> > > > > > selftests: gpio: add CONFIG_GPIO_CDEV to config
> > > > >
> > > > > Bartosz I think you can just merge these patches into the GPIO tree, at least
> > > > > I think that is what I have done in the past.
> > > > >
> > > >
> > > > Could you touch up that Fixes tag in patch 1 if you merge v2?
> > > >
> > > > Thanks,
> > > > Kent.
> > >
> > > Kent,
> > >
> > > This doesn't apply to my for-next branch - there's a conflict in
> > > tools/testing/selftests/gpio/Makefile, could you take a look?
> > >
> >
> > Which is your for-next branch?
> >
> > The patch set is based on and applies cleanly to gpio/for-next 7ac554888233,
> > so I'm not sure which branch you are targetting.
> >
> > Cheers,
> > Kent.
>
> Linus W is not picking up patches this release - everything goes through:
>
> git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
>
> Sorry for the confusion.
>
Ah, ok Michael Ellerman has been improving the Makefile toworkaround
the build dependency issues for some cases.
My changes supersede all that - a basic Makefile is now sufficient.
I'll send out a v3 shortly.
Cheers,
Kent.
prev parent reply other threads:[~2021-01-19 14:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 2:57 [PATCH v2 0/7] selftests: gpio: rework and port to GPIO uAPI v2 Kent Gibson
2021-01-07 2:57 ` [PATCH v2 1/7] selftests: gpio: rework and simplify test implementation Kent Gibson
2021-01-14 15:04 ` Bartosz Golaszewski
2021-01-17 23:54 ` Kent Gibson
2021-01-07 2:57 ` [PATCH v2 2/7] selftests: gpio: remove obsolete gpio-mockup-chardev.c Kent Gibson
2021-01-14 15:04 ` Bartosz Golaszewski
2021-01-07 2:57 ` [PATCH v2 3/7] selftests: remove obsolete build restriction for gpio Kent Gibson
2021-01-14 15:04 ` Bartosz Golaszewski
2021-01-07 2:57 ` [PATCH v2 4/7] selftests: remove obsolete gpio references from kselftest_deps.sh Kent Gibson
2021-01-14 15:05 ` Bartosz Golaszewski
2021-01-07 2:57 ` [PATCH v2 5/7] tools: gpio: remove uAPI v1 code no longer used by selftests Kent Gibson
2021-01-14 15:12 ` Bartosz Golaszewski
2021-01-07 2:57 ` [PATCH v2 6/7] selftests: gpio: port to GPIO uAPI v2 Kent Gibson
2021-01-14 15:13 ` Bartosz Golaszewski
2021-01-07 2:57 ` [PATCH v2 7/7] selftests: gpio: add CONFIG_GPIO_CDEV to config Kent Gibson
2021-01-14 15:13 ` Bartosz Golaszewski
2021-01-18 15:04 ` [PATCH v2 0/7] selftests: gpio: rework and port to GPIO uAPI v2 Linus Walleij
2021-01-19 0:34 ` Kent Gibson
2021-01-19 10:37 ` Bartosz Golaszewski
2021-01-19 10:59 ` Kent Gibson
2021-01-19 11:02 ` Bartosz Golaszewski
2021-01-19 11:21 ` 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=20210119112109.GA23328@sol \
--to=warthog618@gmail.com \
--cc=bamv2005@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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).