public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] two more nvme fixes for Linux 4.15
Date: Wed, 17 Jan 2018 13:30:44 -0700	[thread overview]
Message-ID: <6b19008b-e8fe-d8c0-6794-88f6ff28a510@kernel.dk> (raw)
In-Reply-To: <20180117183622.3nrboga4prjeck5i@infradead.org>

On 1/17/18 11:36 AM, Christoph Hellwig wrote:
> Hi Jens,
> 
> two more last minute fixes for regressions due to the SGL support that
> is new in Linux 4.15.
> 
> The following changes since commit 32835a074171e7b83c1cefbbf9d681bb9518bbd5:
> 
>   Merge branch 'nvme-4.15' of git://git.infradead.org/nvme into for-linus (2018-01-12 10:42:36 -0700)
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/nvme.git nvme-4.15

Something appears to be funky at your end:

git pull --no-ff  git://git.infradead.org/nvme.git nvme-4.15
remote: Counting objects: 12, done.
remote: Compressing objects: 100% (11/11), done.
remote: fatal: unable to read 4276ebfff22ba00fd90e8c241cc7edd56deca353
remote: aborting due to possible repository corruption on the remote side.
fatal: protocol error: bad pack header

-- 
Jens Axboe

  reply	other threads:[~2018-01-17 20:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 18:36 [GIT PULL] two more nvme fixes for Linux 4.15 Christoph Hellwig
2018-01-17 20:30 ` Jens Axboe [this message]
2018-01-17 21:03   ` Christoph Hellwig

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=6b19008b-e8fe-d8c0-6794-88f6ff28a510@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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