From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: raghuhack78@gmail.com, linux-cxl@vger.kernel.org,
ira.weiny@intel.com, bwidawsk@kernel.org,
dan.j.williams@intel.com, vishal.l.verma@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] cxl/mbox: Remove redundant dev_err() after failed mem alloc
Date: Thu, 04 May 2023 12:46:37 +0200 [thread overview]
Message-ID: <2755196.BEx9A2HvPv@suse> (raw)
In-Reply-To: <ZFLaG8jHHXmRp67w@aschofie-mobl2>
On giovedì 4 maggio 2023 00:03:07 CEST Alison Schofield wrote:
> On Wed, May 03, 2023 at 08:32:37PM +0200, Fabio wrote:
> > On venerdì 28 aprile 2023 03:22:34 CEST Raghu H wrote:
[...]
> > >
> > > Signed-off-by: Raghu H <raghuhack78@gmail.com>
> >
> > Is "Raghu H" the name you sign legal documents with?
>
> Fabio,
> Rather than asking a specific question to determine if this is a
> valid SOB, let's just point folks to the documentation to figure
> it out themselves.
> I'm aware that the 'sign legal documents' test
> has been used in the past, but kernel only actually requires a
> known identity.
>
> https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html#sign-you
> r-work-the-developer-s-certificate-of-origin
> https://github.com/cncf/foundation/blob/659fd32c86dc/dco-guidelines.md
Alison,
Thanks for your suggestions.
I have just a couple of questions about this issue...
1) How do we know that the "real name", which the Linux official documentation
refers to, should be interpreted in accordance to the document pointed by the
second link you provided?
I mean, how can we be sure that the official documentation should be
interpreted according to the second link, since it doesn't even cite that
document from CNCF?
Can you provide links to documents / LKML's threads that state agreement of
our Community about the "relaxed" interpretation by CNCF?
2) It looks that some maintainers (e.g., Greg K-H) still interpret "[] using
your real name (sorry, no pseudonyms or anonymous contributions.)" in a
"strict" and "common" sense.
Can you remember that Greg refused all patches from "Kloudifold" and why? If
not, please take a look at the following two questions / objections from Greg:
https://lore.kernel.org/linux-staging/ZCQkPr6t8IOvF6bk@kroah.com/ and
https://lore.kernel.org/linux-staging/ZBCjK2BXhfiFooeO@kroah.com/.
It seems that this issue it's not yet settled.
Am I overlooking something?
Again thanks,
Fabio
> > If not, please send a new version signed-off-by your full legal name.
> > Otherwise... sorry for the noise.
> >
> > Thanks,
> >
> > Fabio
next prev parent reply other threads:[~2023-05-04 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 1:22 [PATCH v2 0/2] Fixing check patch styling issues Raghu H
2023-04-28 1:22 ` [PATCH v2 1/2] cxl/mbox: Remove redundant dev_err() after failed mem alloc Raghu H
2023-05-01 14:52 ` Dave Jiang
2023-05-03 17:57 ` Verma, Vishal L
2023-05-03 18:32 ` Fabio M. De Francesco
2023-05-03 22:03 ` Alison Schofield
2023-05-04 10:46 ` Fabio M. De Francesco [this message]
2023-05-04 15:23 ` Alison Schofield
2023-05-08 4:12 ` RAGHU H
2023-05-03 22:36 ` Davidlohr Bueso
2023-05-04 2:26 ` Alison Schofield
2023-04-28 1:22 ` [PATCH v2 2/2] cxl/region: Remove else after return statement Raghu H
2023-05-01 14:53 ` Dave Jiang
2023-05-03 17:58 ` Verma, Vishal L
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=2755196.BEx9A2HvPv@suse \
--to=fmdefrancesco@gmail.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raghuhack78@gmail.com \
--cc=vishal.l.verma@intel.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