linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@essensium.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH libgpiod-v2] gpiomon: Fix format specifier for uint64_t
Date: Fri, 30 Jul 2021 16:12:50 +0200	[thread overview]
Message-ID: <20210730141249.GA28359@cephalopod> (raw)
In-Reply-To: <CAMRc=Mcmvb24R9RUJk-0QgP+17rMw2Xd9jMff47uUUcOdeA-Lw@mail.gmail.com>

On Thu, Jul 29, 2021 at 04:34:19PM +0200, Bartosz Golaszewski wrote:
[...] 
> Hi Ben!
> 
> This and the other patches are great, thanks!
> 
> I assume they are rebases on top of the next/libpiod-2.0 branch?

That's right.

> I
> want the git repo for libgpiod to remain bisectable and intend to
> switch to the new API in one big patch including the core API, C++ and
> Python bindings as well as test suites. I will keep your patches in my
> queue and apply them once the patch is in master - unless you don't
> care that much about authorship of the patches in which case I can
> squash them into the big patch and credit you in the commit message.
> Let me know what works best for you.

Please squash this one into the big patch (as it fixes a regression in
that) and apply the others separately.

Ben.

-- 
Ben Hutchings · Senior Embedded Software Engineer, Essensium-Mind · mind.be

      reply	other threads:[~2021-07-30 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 13:13 [PATCH libgpiod-v2] gpiomon: Fix format specifier for uint64_t Ben Hutchings
2021-07-29 14:34 ` Bartosz Golaszewski
2021-07-30 14:12   ` Ben Hutchings [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=20210730141249.GA28359@cephalopod \
    --to=ben.hutchings@essensium.com \
    --cc=brgl@bgdev.pl \
    --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).