From: rkuo@codeaurora.org
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Richard Kuo" <rkuo@codeaurora.org>,
linux-kernel@vger.kernel.org,
"Linas Vepstas" <linas@codeaurora.org>
Subject: Re: [PATCH v5 00/36] Hexagon: Add support for Qualcomm Hexagon architecture
Date: Mon, 31 Oct 2011 19:30:08 -0700 (PDT) [thread overview]
Message-ID: <a0e26bc1328fbfe00f01b8e225f2cf1a.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <CA+55aFw2T0_mD1rM+dTz28fZPtSVhVDTWCYxXDvohwCwNk+b2g@mail.gmail.com>
> On Mon, Oct 31, 2011 at 4:58 PM, Richard Kuo <rkuo@codeaurora.org> wrote:
>>
>> Please let me know if there's anything else you require of these
>> patches.
>
> So there's something odd going on with the Sign-off's, which makes me
> unhappy. It also makes me wonder if the authorship is properly
> attributed.
>
> Some of these things are signed off by Linas Vepstas. In fact, some of
> them are *only* signed off on by him, not by you. Which is definitely
> wrong. But it makes me wonder if the authorship is buggered up, and
> those patches maybe should have a "From: Linas Vepstas
> <linas@codeaurora.org>" on them too.
>
> Example of this: "[PATCH v5 12/36] Hexagon: Export ksyms defined in
> assembly files." (but 13/36, 31/36 and 36/36 were that way too).
>
> Others are signed off by both Linas Vepstas and you, but in an odd
> order. Since you're sending them to me, I'd expect your sign-off to be
> last, but it isn't. So the sign-off sequence makes it look like they
> were sent by Linas, even though I got them from you.
>
> So I'd like some clarification on this, and I do need *your* sign-off
> on them all since you're sending them to me.
>
> You don't have to re-send, but you do have to explain whether perhaps
> Linas should be author (and why the odd order of sign-offs) and
> basically do a "yeah, I sign off on those patches" with a full listing
> of the patches in question so that I have it for the record.
>
> Linus
>
OK, my mistake on these. Linas did author those patches, but clearly
I'm in their path. So, I sign off on:
[PATCH v5 12/36] Hexagon: Export ksyms defined in assembly files.
[PATCH v5 13/36] Hexagon: Support dynamic module loading.
[PATCH v5 31/36] Hexagon: kgdb support files
[PATCH v5 36/36] Add extra arch overrides to asm-generic/checksum.h
Many other times, I was the author, and Linas also had contributions to
the files as well, but again, if they're coming through me, my signed-off
should be last. The From: is me because I imported all the files into git
from what we were doing previously. The rest of the patches from now on
should have proper authorship.
Thanks,
Richard Kuo
next prev parent reply other threads:[~2011-11-01 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 23:58 [PATCH v5 00/36] Hexagon: Add support for Qualcomm Hexagon architecture Richard Kuo
2011-11-01 1:10 ` Linus Torvalds
2011-11-01 2:30 ` rkuo [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-19 3:53 Richard Kuo
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=a0e26bc1328fbfe00f01b8e225f2cf1a.squirrel@www.codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=linas@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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