linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] Non-numbered ibm iic driver
Date: Sun, 29 Jun 2008 13:52:32 -0500	[thread overview]
Message-ID: <4867D9F0.1090008@freescale.com> (raw)
In-Reply-To: <20080628232010.2bff2dcc@lappy.seanm.ca>

Sean MacLennan wrote:

> P.S. Do I need a signed-off-by for an RFC?
> 
> Signed-off-by: Sean MacLennan <smaclennan@pikatech.com>
> ---

Not usually.  Some intentionally leave the S-o-b: off of
and RFC specifically to ensure that it stays RFC-ish and
doesn't slip into patchness.

jdl

      parent reply	other threads:[~2008-06-29 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29  3:20 [RFC] Non-numbered ibm iic driver Sean MacLennan
2008-06-29  3:25 ` Jon Smirl
2008-06-29  3:43   ` Sean MacLennan
2008-06-29  4:31     ` Grant Likely
2008-06-29 18:52 ` Jon Loeliger [this message]

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=4867D9F0.1090008@freescale.com \
    --to=jdl@freescale.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).