From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-block@vger.kernel.org
Subject: Re: for-4.15/block rebased
Date: Sat, 11 Nov 2017 15:37:04 -0700 [thread overview]
Message-ID: <d2e9dc7b-28eb-e542-3257-e19855210842@kernel.dk> (raw)
In-Reply-To: <20171111090751.GA13421@infradead.org>
On 11/11/2017 02:07 AM, Christoph Hellwig wrote:
> Yikes. Can you at least re-pull the nvme bits so we can keep
> the original commit dates for those? Those actually are a huge
> part of the rebased commits, and that way we might not get Linus
> shouting at us this merge window at least..
I'm just going to explain my way out of this one instead, I don't
want to do yet another one a day or two before I send it in.
--
Jens Axboe
prev parent reply other threads:[~2017-11-11 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 3:02 for-4.15/block rebased Jens Axboe
2017-11-11 9:07 ` Christoph Hellwig
2017-11-11 22:37 ` Jens Axboe [this message]
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=d2e9dc7b-28eb-e542-3257-e19855210842@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.