From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
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:03:21 -0800 [thread overview]
Message-ID: <20180117210321.GA20324@infradead.org> (raw)
In-Reply-To: <6b19008b-e8fe-d8c0-6794-88f6ff28a510@kernel.dk>
On Wed, Jan 17, 2018 at 01:30:44PM -0700, Jens Axboe wrote:
> 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
The repo did have corruption due to an unclean shutdown of the
git.infradead.org machine and gits unsafe defaults. But I'm totally
lost on how to fix this, so I'll just send the patch series to you
instead.
prev parent reply other threads:[~2018-01-17 21:03 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
2018-01-17 21:03 ` Christoph Hellwig [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=20180117210321.GA20324@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--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