From: Jens Axboe <axboe@fb.com>
To: Keith Busch <keith.busch@intel.com>,
Wang Weber <mail.weber.wang@gmail.com>
Cc: <linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvme/quirk: Add a delay before checking device ready for memblaze device
Date: Thu, 8 Sep 2016 09:02:30 -0600 [thread overview]
Message-ID: <71e083c9-6bef-2da1-5eeb-fa6c6028c8c3@fb.com> (raw)
In-Reply-To: <d56137f2-77b7-cae7-4048-2e740bd47c7f@fb.com>
On 09/08/2016 08:30 AM, Jens Axboe wrote:
> On 09/08/2016 08:36 AM, Keith Busch wrote:
>> On Thu, Sep 08, 2016 at 11:36:34AM +0800, Wang Weber wrote:
>>> Hi Jens,
>>>
>>> The following email was sent before, but it seems to be blocked since I
>>> received some messages about sending failure. So resend it with Google
>>> email account.
>>
>> You're still sending non plain text email, so it's going to be rejected
>> by the mailing list filter. It also mangles your patch such that it
>> won't cleanly apply. You have to use plain text for this to work well.
>
> Indeed. And in addition to it being rejected by the reflector, it also
> means your patch is mangled.
I guess Keith already made that point too on the patch mangling, needs
more coffee. Also, it mangles the patch.
--
Jens Axboe
next prev parent reply other threads:[~2016-09-08 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAZN+A3m4z0uOUBWyonpXb2fQTuFhV3vu68Kuy4mdQYwt6WDgA@mail.gmail.com>
2016-09-08 14:36 ` Keith Busch
2016-09-08 14:30 ` Jens Axboe
2016-09-08 15:02 ` Jens Axboe [this message]
2016-09-08 16:12 Wenbo Wang
2016-09-08 16:18 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2016-08-15 5:21 Wenbo Wang
2016-08-15 15:05 ` Keith Busch
2016-08-09 3:18 Wenbo Wang
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=71e083c9-6bef-2da1-5eeb-fa6c6028c8c3@fb.com \
--to=axboe@fb.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mail.weber.wang@gmail.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
Powered by JetHome