From: David Woodhouse <dwmw2@infradead.org>
To: "Weil, Oren jer" <oren.jer.weil@intel.com>
Cc: Greg KH <gregkh@suse.de>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [RFC PATCH 01/13] Intel(R) MEI Driver
Date: Fri, 11 Feb 2011 10:19:02 +0100 [thread overview]
Message-ID: <1297415942.16513.40.camel@macbook.infradead.org> (raw)
In-Reply-To: <F28B59AD52D84B479DCA46982447533506505D9ACE@hasmsx503.ger.corp.intel.com>
On Fri, 2011-02-11 at 10:57 +0200, Weil, Oren jer wrote:
>
> 1) For the review purpose we wanted to split the patches into files, so the
> only way we found to do it is using "git diff", this is they there is not
> signed-off-by line
So you type it manually, when you're setting an appropriate subject and
typing your coherent explanation of what's in each patch, and how it
fits together.
--
dwmw2
next prev parent reply other threads:[~2011-02-11 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 9:54 [RFC PATCH 01/13] Intel(R) MEI Driver Oren Weil
2011-02-10 16:50 ` Randy Dunlap
2011-02-10 18:00 ` Greg KH
2011-02-11 8:57 ` Weil, Oren jer
2011-02-11 9:19 ` David Woodhouse [this message]
2011-02-11 14:53 ` Greg KH
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=1297415942.16513.40.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oren.jer.weil@intel.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