From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Farhan Ali <alifm@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: linux-next: Fixes tag needs some work in the s390-fixes tree
Date: Wed, 24 Jul 2019 07:54:12 +0200 [thread overview]
Message-ID: <20190724055412.GB4412@osiris> (raw)
In-Reply-To: <20190724074227.63abe116@canb.auug.org.au>
Hi Stephen,
On Wed, Jul 24, 2019 at 07:42:27AM +1000, Stephen Rothwell wrote:
> In commit
> 8b515be512a2 ("vfio-ccw: Fix memory leak and don't call cp_free in cp_init")
> Fixes tag
> Fixes: 812271b910 ("s390/cio: Squash cp_free() and cp_unpin_free()")
> - 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").
Yes, I noticed this when merging the vfio tree, but decided to not
ask for a rebase to fix this.
Are your scripts that do sanity checks available somewhere? I'm
wondering since I would also like to do some sanity checks before
pushing updates to kernel.org like
- has the git author signed off the patch?
- has the git committer signed off the patch?
- are "fixes" tags sane: does commit exist and is format ok?
prev parent reply other threads:[~2019-07-24 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 21:42 linux-next: Fixes tag needs some work in the s390-fixes tree Stephen Rothwell
2019-07-24 5:54 ` Heiko Carstens [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=20190724055412.GB4412@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=gor@linux.ibm.com \
--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