All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs.
Date: Mon, 7 Mar 2022 17:30:02 +0800	[thread overview]
Message-ID: <20220307093002.GA45584@sol> (raw)
In-Reply-To: <CAMRc=MebW6P0qDi0DNckwVe2+LX3Bi84-HPZPGnAA-tvDiJ9Xg@mail.gmail.com>

On Mon, Mar 07, 2022 at 10:16:49AM +0100, Bartosz Golaszewski wrote:
> On Sat, Mar 5, 2022 at 10:40 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > Having the libgpiod documentation available online would be helpful, so
> > add the configuration required to generate the existing doxygen C/C++
> > documentation on readthedocs.
> >
> > Signed-off-by: Kent Gibson <warthog618@gmail.com>
> >

[snip]

> > --- /dev/null
> > +++ b/sphinx/index.rst
> > @@ -0,0 +1,24 @@
> > +.. SPDX-License-Identifier: LGPL-2.1-or-later
> > +
> > +..
> > +   This file is part of libgpiod.
> > +
> > +   Copyright (C) 2022 Bartosz Golaszewski <bartekgola@gmail.com>
> 
> All looks good to me except that Copyright should be yours here, not mine. :)
> 

Seemed simpler to me to keep it under the one umbrella, so happy to
transfer any and all copyrights to you.

Cheers,
Kent.

  reply	other threads:[~2022-03-07  9:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05  9:40 [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs Kent Gibson
2022-03-07  9:16 ` Bartosz Golaszewski
2022-03-07  9:30   ` Kent Gibson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-10  2:01 Kent Gibson
2023-06-10  5:20 ` kernel test robot
2023-06-10  5:43   ` Kent Gibson
2023-06-12 12:58     ` Bartosz Golaszewski
2023-06-12 13:40       ` Philip Li
2023-06-10  5:42 ` kernel test robot
2023-06-12 16:27 ` Bartosz Golaszewski
2023-06-12 16:40   ` Kent Gibson
2023-06-12 17:30     ` Bartosz Golaszewski

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=20220307093002.GA45584@sol \
    --to=warthog618@gmail.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 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.