From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Kent Gibson <warthog618@gmail.com>,
linux-gpio <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod][PATCH v2 2/2] core: fix reading subset of available events
Date: Mon, 14 Sep 2020 18:22:42 +0300 [thread overview]
Message-ID: <CAHp75VctD2B6thMatpEAM8N4z06=D_JbES0Dt5gPxgB==79ZMQ@mail.gmail.com> (raw)
In-Reply-To: <CAMpxmJUHcFsoREWoqqS5y7ZhOm=KqquJ0LDkUj7C2ZvtmTps9w@mail.gmail.com>
On Mon, Sep 14, 2020 at 6:20 PM Bartosz Golaszewski
<bgolaszewski@baylibre.com> wrote:
> On Mon, Sep 14, 2020 at 5:16 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> >
> > On Mon, Sep 14, 2020 at 11:16 AM Bartosz Golaszewski
> > <bgolaszewski@baylibre.com> wrote:
> > > On Sat, Sep 12, 2020 at 10:11 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > > > Fixes: 44921ecc9a00 (core: provide functions for reading multiple
> > > > line events at once)
> > > >
> > > > Signed-off-by: Kent Gibson <warthog618@gmail.com>
> >
> >
> > > Will apply shortly and backport it to stable branches too.
> >
> > Please note that
> > - Fixes (or actually any tag) should be one per line
> > - no blank lines in the tag block
> >
>
> Kent: no need to resend this, I fixed it when applying, but yeah for
> the future it's true.
JFYI: I'm about to look at v8 patch 4 of uAPI v2 series.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-09-14 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 8:11 [libgpiod][PATCH v2 0/2] fix potential discarding of events by read events Kent Gibson
2020-09-12 8:11 ` [libgpiod][PATCH v2 1/2] tests: event: reading test coverage extended to cover reading a subset of available events Kent Gibson
2020-09-12 8:11 ` [libgpiod][PATCH v2 2/2] core: fix reading " Kent Gibson
2020-09-14 8:12 ` Bartosz Golaszewski
2020-09-14 15:16 ` Andy Shevchenko
2020-09-14 15:20 ` Bartosz Golaszewski
2020-09-14 15:22 ` Andy Shevchenko [this message]
2020-09-14 23:33 ` 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='CAHp75VctD2B6thMatpEAM8N4z06=D_JbES0Dt5gPxgB==79ZMQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=linux-gpio@vger.kernel.org \
--cc=warthog618@gmail.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.