All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>,
	Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Andy Whitcroft <apw@canonical.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Tobin C . Harding" <me@tobin.cc>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Niklas Cassel <niklas.cassel@linaro.org>
Subject: Re: [PATCH v5 1/2] docs: Clarify the usage and sign-off requirements for Co-developed-by
Date: Mon, 25 Mar 2019 09:40:32 -0700	[thread overview]
Message-ID: <65a633806b819c3067972853a9f1c2b6029e0ce5.camel@perches.com> (raw)
In-Reply-To: <20190325103114.2df3b91d@lwn.net>

On Mon, 2019-03-25 at 10:31 -0600, Jonathan Corbet wrote:
> On Fri, 22 Mar 2019 14:11:36 -0700 Sean Christopherson <sean.j.christopherson@intel.com> wrote:
> > The documentation for Co-developed-by is a bit light on details,
[]
> I've applied this.  Joe, do you want to handle the checkpatch.pl patch, or
> would you prefer I take that one too?

You taking it is fine with me.



  reply	other threads:[~2019-03-25 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 21:11 [PATCH v5 0/2] docs: checkpatch: improve handling of Co-developed-by Sean Christopherson
2019-03-22 21:11 ` [PATCH v5 1/2] docs: Clarify the usage and sign-off requirements for Co-developed-by Sean Christopherson
2019-03-23  2:00   ` Tobin C. Harding
2019-03-25 16:31   ` Jonathan Corbet
2019-03-25 16:40     ` Joe Perches [this message]
2019-03-25 16:45       ` Jonathan Corbet
2019-03-22 21:11 ` [PATCH v5 2/2] checkpatch: Warn on improper usage of Co-developed-by Sean Christopherson
2019-03-23  2:01   ` Tobin C. Harding

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=65a633806b819c3067972853a9f1c2b6029e0ce5.camel@perches.com \
    --to=joe@perches.com \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jic23@kernel.org \
    --cc=jorge.ramirez-ortiz@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --cc=niklas.cassel@linaro.org \
    --cc=sean.j.christopherson@intel.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.