mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] libgpiod: new package
Date: Fri, 26 May 2017 10:57:05 +0200	[thread overview]
Message-ID: <20170526085705.gs3wun34aikjaqmf@pengutronix.de> (raw)
In-Reply-To: <20170524171158.GA29979@archie.localdomain>

On Wed, May 24, 2017 at 07:11:59PM +0200, Clemens Gruber wrote:
> On Wed, May 24, 2017 at 06:43:16PM +0200, Robert Schwebel wrote:
> > On Wed, May 24, 2017 at 05:09:19PM +0200, Clemens Gruber wrote:
> > > libgpiod is a C library with tools for interacting with the Linux
> > > GPIO character device. Add a package for it.
> > > 
> > > Note: Requires kernel-headers >= 4.8.
> > > 
> > > Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>
> > > ---
> > 
> > This should have a changelog below the tripledash.
> 
> Right. Not sure if I should resend though, as the changelog will not
> show up in the commit message.
> Let me know if you want me to resend the patch with the changelog
> anyway.
> 
> Changes since v1:
> - Added the kernel-headers include directory to CPPFLAGS
> - Added some warning notes/comments that >= v4.8 is required

Is this a copy of the kernel's tools/gpio directory? If so, I'd prefer
to stick to the official source.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-05-26  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 15:09 Clemens Gruber
2017-05-24 16:43 ` Robert Schwebel
2017-05-24 17:11   ` Clemens Gruber
2017-05-26  8:57     ` Uwe Kleine-König [this message]
2017-05-26  9:29       ` Clemens Gruber

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=20170526085705.gs3wun34aikjaqmf@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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