From: Christoph Hellwig <hch@infradead.org>
To: James Smart <james.smart@emulex.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/19] lpfc 10.4.8000.0: Update lpfc version to driver version 10.4.8000.0
Date: Thu, 4 Sep 2014 22:35:32 -0700 [thread overview]
Message-ID: <20140905053532.GA10457@infradead.org> (raw)
In-Reply-To: <1409763288.12357.0.camel@myfc17>
I've applied the series, but for next time can you make sure to follow
the proper format:
- remove the version number in every subject line
- patches you resend from an original author should be unchanged,
except that the From: lines moves into the mail body
- patches that you send on with your maintainer hat on should be
signed off by you, not just reviewed.
not strictly required, but making my life a lot easier would be if all
patches are sent by reply to the original mail. git-send-email does
this, and it seems like the Emulex division supporting be2scsi has found
a way to use it with the corporate email servers.
next prev parent reply other threads:[~2014-09-05 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 16:54 [PATCH 0/19] lpfc 10.4.8000.0: Update lpfc version to driver version 10.4.8000.0 James Smart
2014-09-05 5:35 ` Christoph Hellwig [this message]
2014-09-05 13:31 ` James Smart
2014-09-05 13:59 ` James Bottomley
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=20140905053532.GA10457@infradead.org \
--to=hch@infradead.org \
--cc=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.org \
/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