linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: [PATCH] Hwmon for Taco
Date: Tue, 8 Jan 2008 23:13:14 +0300	[thread overview]
Message-ID: <20080108201314.GA29127@localhost.localdomain> (raw)
In-Reply-To: <20080108130251.7ae351c7@zod.rchland.ibm.com>

On Tue, Jan 08, 2008 at 01:02:51PM -0600, Josh Boyer wrote:
> On Tue, 08 Jan 2008 13:30:00 -0500
> Sean MacLennan <smaclennan@pikatech.com> wrote:
> 
> > Ok, here is the ad7414 only. taco-dtm is no more!
> 
> Cool.  Couple more things.
> 
> 1) This should go through the hwmon maintainer.  Send it to him.
> (CC'ing this list is of course fine.)
> 
> 2) You always need the Signed-off-by: for each patch you send
> 
> 3) If you didn't author the code (this seems to come from Stefan), then
> you need the Signed-off-by from the original author.

Nope. Signed-off-by means completely different thing. It isn't
copyright, it isn't authorship. It's an information (for the history)
whom to bother if code appeared to be either:
a) broken;
b) stolen from the closed source product;
c) patented (where applicable).

There are Copyright (c) and Author: strings in the files for the
credits. If original patch had these strings, then yes, you must
keep them.

But no one needs author's Signed-off-by, it having zero information
you're hinting about. More than that, there were precedents when
author insisted on removing his Signed-off-by from the modified
patch (when S-o-b used as a permit into someone's tree).

Btw, kernel.org is distributing linux tarballs without changelogs,
thus without Signed-off-by lines. Nobody complains.


Yes, it's common sense and politeness to keep Signed-off-by lines
intact (and the order of these lines), but it's not strict
requirement. "Based on the patch from ..." is the equivalent of
this politeness.

> You're getting there :)  These are all "newbie" type mistakes so keep
> plugging away.
> 
> josh

Good luck,

-- 
Anton Vorontsov
email: cbou@mail.ru
backup email: ya-cbou@yandex.ru
irc://irc.freenode.net/bd2

  parent reply	other threads:[~2008-01-08 20:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05  5:11 [PATCH] Hwmon for Taco Sean MacLennan
2008-01-05  7:22 ` Benjamin Herrenschmidt
2008-01-05 18:39   ` Sean MacLennan
2008-01-08  6:30   ` Sean MacLennan
2008-01-08  6:59     ` Grant Likely
2008-01-08 18:09       ` Sean MacLennan
2008-01-08 18:30       ` Sean MacLennan
2008-01-08 19:02         ` Josh Boyer
2008-01-08 19:27           ` Stefan Roese
2008-01-08 20:13           ` Anton Vorontsov [this message]
2008-01-08 20:20             ` Josh Boyer

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=20080108201314.GA29127@localhost.localdomain \
    --to=avorontsov@ru.mvista.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=smaclennan@pikatech.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;
as well as URLs for NNTP newsgroup(s).