public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: matoro <matoro_mailinglist_kernel@matoro.tk>
Cc: Sergei Trofimovich <slyich@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64: fix clock_getre(CLOCK_MONOTONIC) to report ITC frequency
Date: Sat, 20 Aug 2022 15:14:38 -0700	[thread overview]
Message-ID: <20220820151438.d55718d341df99d5747caebb@linux-foundation.org> (raw)
In-Reply-To: <6d07209d000b671a3bc48003905652e8@matoro.tk>

On Wed, 17 Aug 2022 17:57:42 -0400 matoro <matoro_mailinglist_kernel@matoro.tk> wrote:

> Hi Andrew, I came up with the prototype for this patch, but it was based 
> entirely on Sergei's investigation which was documented in 
> https://bugs.gentoo.org/596382.  I asked him to send it upstream because 
> I'm unable to attach my realname to it due to my job.

In that case it's unclear that your Signed-off-by: is appropriate?

: Developer's Certificate of Origin 1.1
: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
: 
: By making a contribution to this project, I certify that:
: 
:         (a) The contribution was created in whole or in part by me and I
:             have the right to submit it under the open source license
:             indicated in the file; or
: 
:         (b) The contribution is based upon previous work that, to the best
:             of my knowledge, is covered under an appropriate open source
:             license and I have the right under that license to submit that
:             work with modifications, whether created in whole or in part
:             by me, under the same open source license (unless I am
:             permitted to submit under a different license), as indicated
:             in the file; or
: 
:         (c) The contribution was provided directly to me by some other
:             person who certified (a), (b) or (c) and I have not modified
:             it.
: 
:         (d) I understand and agree that this project and the contribution
:             are public and that a record of the contribution (including all
:             personal information I submit with it, including my sign-off) is
:             maintained indefinitely and may be redistributed consistent with
:             this project or the open source license(s) involved.


>  I can place a 
> signed-off-by with my handle but I understand that's normally against 
> kernel policy which is why I didn't.  Either way the bulk of the work 
> belongs to Sergei, I just scribbled it down, and he cleaned it up for 
> this submission.

I think I'll switch it to a Cc: :)

  reply	other threads:[~2022-08-20 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  5:49 [PATCH] ia64: fix clock_getre(CLOCK_MONOTONIC) to report ITC frequency Sergei Trofimovich
2022-08-17 19:21 ` Andrew Morton
2022-08-17 21:57   ` matoro
2022-08-20 22:14     ` Andrew Morton [this message]
2022-09-10 17:50       ` [PATCH v3] ia64: fix clock_getres(CLOCK_MONOTONIC) " Sergei Trofimovich
2022-08-20 18:17   ` [PATCH] ia64: fix clock_getre(CLOCK_MONOTONIC) " Sergei Trofimovich
2022-08-20 18:18     ` [PATCH v2] ia64: fix clock_getres(CLOCK_MONOTONIC) " Sergei Trofimovich

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=20220820151438.d55718d341df99d5747caebb@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matoro_mailinglist_kernel@matoro.tk \
    --cc=slyich@gmail.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