public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Erik Schilling <erik.schilling@linaro.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Linus Walleij <linus.walleij@linaro.org>,
	Phil Howard <phil@gadgetoid.com>,
	linux-gpio@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH] README: add info about the github page
Date: Sat, 13 Jan 2024 09:57:35 +0800	[thread overview]
Message-ID: <20240113015735.GA3233@rigel> (raw)
In-Reply-To: <CYCV04Z0DTXJ.EL52UULK796I@ablu-work>

On Fri, Jan 12, 2024 at 05:13:37PM +0100, Erik Schilling wrote:
> On Fri Jan 12, 2024 at 5:05 PM CET, Bartosz Golaszewski wrote:
> > On Fri, Jan 12, 2024 at 4:26 PM Erik Schilling
> > <erik.schilling@linaro.org> wrote:
> > >
> > > disabled for the public.
> > >
> > > - Erik
> > >
> >
> > Should be good now.
>
> Reviewed-by: Erik Schilling <erik.schilling@linaro.org>
>
> > Should I create a wiki too?
>
> Got no opinion on that.
>

I think the wiki could be useful for linking to things that aren't in
the README or that you can't readily link to with a plain text README,
like links to the readthedocs documentation, kernel patch submission
process, maybe some hints on building for different distros (e.g. to
identify packages that need to be installed first)....

And speaking of the README, just noticed it mentions 4.8 as being the
first release of the uAPI, but libgpiod uses v2 exclusively, and that wasn't
introduced until 5.10.  We might want to update that - still mention 4.8,
since you also mention deprecating sysfs, but also mention v2 and 5.10.

Cheers,
Kent.

      reply	other threads:[~2024-01-13  1:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 15:05 [libgpiod][PATCH] README: add info about the github page Bartosz Golaszewski
2024-01-12 15:25 ` Kent Gibson
2024-01-12 15:40   ` Kent Gibson
2024-01-12 16:07     ` Bartosz Golaszewski
2024-01-12 16:18       ` Erik Schilling
2024-01-15  9:37         ` Bartosz Golaszewski
2024-01-13  2:25       ` Kent Gibson
2024-01-12 15:26 ` Erik Schilling
2024-01-12 16:05   ` Bartosz Golaszewski
2024-01-12 16:13     ` Erik Schilling
2024-01-13  1:57       ` 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=20240113015735.GA3233@rigel \
    --to=warthog618@gmail.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=erik.schilling@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=phil@gadgetoid.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox