From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: "Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Jon Loeliger <loeliger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] fdtoverlay: Fix usage string to not mention "<type>"
Date: Mon, 20 Jun 2022 19:45:19 +1000 [thread overview]
Message-ID: <YrBBrzP0Xmd0B29Z@yekko> (raw)
In-Reply-To: <20220620072918.uxqg3w2wzjdagx2o-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2707 bytes --]
On Mon, Jun 20, 2022 at 09:29:18AM +0200, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Mar 24, 2022 at 09:35:18AM +0100, Uwe Kleine-König wrote:
> > On Thu, Mar 24, 2022 at 11:48:22AM +1100, David Gibson wrote:
> > > On Wed, Mar 23, 2022 at 08:46:52AM +0100, Uwe Kleine-König wrote:
> > > > Hello David,
> > > >
> > > > On Wed, Mar 23, 2022 at 12:54:19PM +1100, David Gibson wrote:
> > > > > On Tue, Mar 22, 2022 at 09:08:59AM +0100, Uwe Kleine-König wrote:
> > > > > > fdtoverlay doesn't have a -t option, so explaining the type formats and
> > > > > > modifier prefixes doesn't make much sense.
> > > > > > ---
> > > > > > Hello,
> > > > > >
> > > > > > I was unsure if I'm supposed to add a signed-off-by line. It's not
> > > > > > formalized in the git repo, so I assume it won't have any juristical
> > > > > > semantic anyhow and I didn't add it.
> > > > >
> > > > > It's true we've never formalized this, but I do generally prefer S-o-b
> > > > > lines to be present.
> > > > >
> > > > > The patch LGTM, so if you could resent with the signoff I'll apply.
> > > >
> > > > Then I wonder about the semantic of the Signed-off-by for dtc. Do you
> > > > believe it has any juristical effect if you don't give it an explicit
> > > > meaning for the project? INAL, but it feels wrong to me to insist on a
> > > > formalism but not having formalized its meaning.
> > >
> > > Well, I'm not really sure what you mean by "juristical effect".
> >
> > For kernel patches (and quite a few other projects that adopted the
> > "Developer's Certificate of Origin", I'd expect that as a maintainer or
> > user of the project you can assume that there are no license problems
> > with the contribution.
> >
> > > AFAIK the S-o-b lines never have any legal force, as such - they're
> > > just a form of documentation that helps to locate the right people to
> > > contact if legal questions show up in future.
> >
> > Even without S-o-b I'm listed in the Author line, isn't that enough for
> > providing a point of contact?
>
> This patch wasn't applied and the S-o-b discussion just died.
>
> In my eyes the options here are:
>
> a) just apply the patch as is
> b) formalize the meaning of S-o-b and then I can resend with my
> signature (assuming I agree to the formalization).
>
> I don't have a strong opinion here, but my favourite would be a) as it's
> less work for me.
I've been meaning to do (b), but I just haven't gotten around to it.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-20 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 8:08 [PATCH] fdtoverlay: Fix usage string to not mention "<type>" Uwe Kleine-König
[not found] ` <20220322080859.230337-1-u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2022-03-23 1:54 ` David Gibson
2022-03-23 7:46 ` Uwe Kleine-König
[not found] ` <20220323074652.kbslenf73cyjaso6-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2022-03-24 0:48 ` David Gibson
2022-03-24 8:35 ` Uwe Kleine-König
[not found] ` <20220324080451.za5eukns7ptisztx-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2022-06-20 7:29 ` Uwe Kleine-König
[not found] ` <20220620072918.uxqg3w2wzjdagx2o-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2022-06-20 9:45 ` David Gibson [this message]
2022-07-28 7:55 ` David Gibson
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=YrBBrzP0Xmd0B29Z@yekko \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=loeliger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).