From: Kent Gibson <warthog618@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
linux-gpio <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod][PATCH v2 2/2] core: fix reading subset of available events
Date: Tue, 15 Sep 2020 07:33:02 +0800 [thread overview]
Message-ID: <20200914233302.GB4138@sol> (raw)
In-Reply-To: <CAHp75VeFWQCkeXne+7i2FEUNy97yjPiMwsQqkm7mqhtXiGac7A@mail.gmail.com>
On Mon, Sep 14, 2020 at 06:16:35PM +0300, Andy Shevchenko 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
>
Sorry - I wasn't aware that tags are exempt to the line length limits.
And checkpatch.pl doesn't pick up those rules either :-(.
Cheers,
Kent.
prev parent reply other threads:[~2020-09-14 23:33 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
2020-09-14 23:33 ` 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=20200914233302.GB4138@sol \
--to=warthog618@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=linux-gpio@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 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).