From: Jeff Moyer <jmoyer@redhat.com>
To: "Sam Bradshaw \(sbradshaw\)" <sbradshaw@micron.com>
Cc: <jaxboe@fusionio.com>, <alan@lxorguk.ukuu.org.uk>,
<hch@infradead.org>, <linux-ide@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, "Jeff Garzik" <jgarzik@pobox.com>,
"Asai Thambi Samymuthu Pattrayasamy \(asamymuthupa\)
\[CONTRACTOR\]" <asamymuthupa@micron.com>
Subject: Re: [PATCH v4] drivers/block/mtip32xx: Adding new driver mtip32xx
Date: Thu, 01 Sep 2011 15:43:09 -0400 [thread overview]
Message-ID: <x49y5y8xd4i.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <2A9BE4FF6209B644B6F8EB62DE6AEA1E07663ED4@ntxfrembx01.micron.com> (Sam Bradshaw's message of "Mon, 22 Aug 2011 14:28:11 -0700")
"Sam Bradshaw (sbradshaw)" <sbradshaw@micron.com> writes:
> New patch for mtip32xx driver based on feedback from
> Jens Axboe, Christoph Hellwig, and Alan Cox.
Hi, Sam,
The patch is line-wrapped. Could you fix your mailer settings and
re-send?
Thanks,
Jeff
next prev parent reply other threads:[~2011-09-01 19:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 18:52 [PATCH v3 2/3] drivers/block/mtip32xx: Adding source for hardware related operations Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-08-12 8:42 ` Jens Axboe
2011-08-18 0:18 ` Asai Thambi S P
2011-08-22 21:28 ` [PATCH v4] drivers/block/mtip32xx: Adding new driver mtip32xx Sam Bradshaw (sbradshaw)
2011-09-01 19:43 ` Jeff Moyer [this message]
2011-09-01 19:46 ` Jens Axboe
2011-09-09 8:54 ` Christoph Hellwig
2011-09-09 8:58 ` Jens Axboe
2011-09-09 9:02 ` Christoph Hellwig
2011-09-09 15:10 ` Sam Bradshaw (sbradshaw)
2011-09-12 15:02 ` Christoph Hellwig
2011-09-12 18:25 ` Jens Axboe
2011-09-30 13:33 ` Christoph Hellwig
2011-09-30 19:45 ` Asai Thambi S P
2011-09-30 21:20 ` Jens Axboe
2011-09-30 19:49 ` Asai Thambi S P
2011-09-13 12:49 ` Christoph Hellwig
2011-09-13 16:46 ` Eric Seppanen
2011-09-13 21:03 ` Jens Axboe
[not found] <2A9BE4FF6209B644B6F8EB62DE6AEA1E07765C71@ntxfrembx01.micron.com>
2011-09-01 22:23 ` Sam Bradshaw
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=x49y5y8xd4i.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=asamymuthupa@micron.com \
--cc=hch@infradead.org \
--cc=jaxboe@fusionio.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sbradshaw@micron.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).