public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jing Huang <huangj@Brocade.COM>
Cc: Greg KH <greg@kroah.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ramkumar Vadivelu <rvadivel@Brocade.COM>,
	Vinodh Ravindran <vravindr@Brocade.COM>,
	"Srikanth Rayas (CW)" <srayas@Brocade.COM>
Subject: RE: [PATCH 1/6] bfa: Brocade BFA FC SCSI Driver submission
Date: Wed, 24 Sep 2008 22:41:20 -0700	[thread overview]
Message-ID: <1222321280.3602.10.camel@localhost.localdomain> (raw)
In-Reply-To: <4C94DE2070B172459E4F1EE14BD2364E01F27D49@HQ-EXCH-5.corp.brocade.com>

On Wed, 2008-09-24 at 22:33 -0700, Jing Huang wrote:
> Thanks James and Greg for the quick check on the patches.
> 
> I check the original patch, it is correct. I need to check the outlook
> setting to see how to prevent this issue.
> 
> This is my first time sending a patch, is there any trick to prevent
> line-wrap? I did send it using plain text and I tried to send to myself
> before sending to lkml, and I did't see this problem.
> 
> Sorry about the trouble.

Unfortunately, the remedy tends to be fairly specific to the email tool
you're using.  There's a helpful list of what to do here:

Documentation/email-clients.txt

but it's not exhaustive.

James

  reply	other threads:[~2008-09-25  5:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25  3:56 [PATCH 1/6] bfa: Brocade BFA FC SCSI Driver submission Jing Huang
2008-09-25  4:49 ` Greg KH
2008-09-25  5:14   ` James Bottomley
2008-09-25  5:33     ` Jing Huang
2008-09-25  5:41       ` James Bottomley [this message]
     [not found]       ` <20080925055725.GC66712@sgi.com>
2008-09-25  6:09         ` Jing Huang
2008-09-25 15:34           ` James Bottomley
2008-09-25 16:56             ` Jing Huang

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=1222321280.3602.10.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=greg@kroah.com \
    --cc=huangj@Brocade.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rvadivel@Brocade.COM \
    --cc=srayas@Brocade.COM \
    --cc=vravindr@Brocade.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