From: Bjorn Helgaas <bjorn.helgaas@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: Fixes tag needs some work in the pci-current tree
Date: Mon, 17 Aug 2020 17:09:00 -0500 [thread overview]
Message-ID: <CABhMZUUzSQQZbySX6-E6JL8nBd8fc=cfSjih9LWJk0C-H8C=eQ@mail.gmail.com> (raw)
In-Reply-To: <20200818075918.15ac1099@canb.auug.org.au>
On Mon, Aug 17, 2020 at 4:59 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> 35150fc886a0 ("PCI/P2PDMA: Fix build without DMA ops")
>
> Fixes tag
>
> Fixes: 2f9237d4f6d ("dma-mapping: make support for dma ops optional")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> or later) just making sure it is not set (or set to "auto").
Fixed, thanks.
prev parent reply other threads:[~2020-08-17 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 21:59 linux-next: Fixes tag needs some work in the pci-current tree Stephen Rothwell
2020-08-17 22:09 ` Bjorn Helgaas [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='CABhMZUUzSQQZbySX6-E6JL8nBd8fc=cfSjih9LWJk0C-H8C=eQ@mail.gmail.com' \
--to=bjorn.helgaas@gmail.com \
--cc=bhelgaas@google.com \
--cc=bjorn@helgaas.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).