Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "René Bolldorf" <xsecute@googlemail.com>
Cc: Gabor Juhos <juhosg@openwrt.org>,
	Sergei Shtylyov <sshtylyov@mvista.com>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH v3 3/7] MIPS: ath79: make ath724x_pcibios_init visible for external code
Date: Mon, 21 Nov 2011 14:31:43 +0000	[thread overview]
Message-ID: <20111121143143.GA13340@linux-mips.org> (raw)
In-Reply-To: <CAEWqx5_Zep8QwS2t32BpygbqXx0exE4kTsH07J=vW2zr7rVO_w@mail.gmail.com>

On Mon, Nov 21, 2011 at 02:58:50PM +0100, René Bolldorf wrote:

> The sob tag is only for persons that are involved in the development
> of the patch.
> 
> Acked-by: Rene Bolldorf <xsecute@googlemail.com>

Since the header file in question was taken from a patch that you had
signed off, it would have been acceptable for Gábor to add a SoB line
for you to this patch in addition to his own.

Documentation/SubmittinPatches defines the semantics of SoB as:

 < ------------ snip snap snop ----------- >

        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.

then you just add a line saying

        Signed-off-by: Random J Developer <random@developer.example.org>

 < ------------ snip snap snop ----------- >

I'm normally accept non-trivial patches with just a single SoB line though
I might ask for the original author(s)' SoB in some cases or might just
complain missing SoBs and apply a patch anyway if it's trivial which means
like 10 lines of not quite rocket science content.

  Ralf

  reply	other threads:[~2011-11-21 14:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20 21:39 [PATCH v3 0/7] MIPS: ath79: cleanup AR724X PCI support code Gabor Juhos
2011-11-20 21:39 ` [PATCH v3 1/7] MIPS: ath79: separate common PCI code Gabor Juhos
2011-11-21 13:53   ` René Bolldorf
2011-11-20 21:39 ` [PATCH v3 2/7] MIPS: ath79: rename pci-ath724x.h Gabor Juhos
2011-11-21 13:52   ` René Bolldorf
2011-11-20 21:39 ` [PATCH v3 3/7] MIPS: ath79: make ath724x_pcibios_init visible for external code Gabor Juhos
2011-11-21 10:19   ` Sergei Shtylyov
2011-11-21 11:53     ` Gabor Juhos
2011-11-21 13:58       ` René Bolldorf
2011-11-21 14:31         ` Ralf Baechle [this message]
2011-11-20 21:39 ` [PATCH v3 4/7] MIPS: ath79: add a common PCI registration function Gabor Juhos
2011-11-21 10:17   ` Sergei Shtylyov
2011-11-21 11:58     ` Gabor Juhos
2011-11-20 21:39 ` [PATCH v3 5/7] MIPS: ath79: rename pci-ath724x.c to make it reflect the real SoC name Gabor Juhos
2011-11-21 13:52   ` René Bolldorf
2011-11-20 21:39 ` [PATCH v3 6/7] MIPS: ath79: replace ath724x to ar724x Gabor Juhos
2011-11-21 13:55   ` René Bolldorf
2011-11-20 21:39 ` [PATCH v3 7/7] MIPS: ath79: use io-accessor macros in pci-ar724x.c Gabor Juhos
2011-11-21 13:54   ` René Bolldorf

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=20111121143143.GA13340@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=juhosg@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=sshtylyov@mvista.com \
    --cc=xsecute@googlemail.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