linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Guillem Jover <guillem@hadrons.org>
Subject: linux-next: Fixes tag needs some work in the vfs-fixes tree
Date: Tue, 22 Oct 2019 07:44:26 +1100	[thread overview]
Message-ID: <20191022074426.2c0a2485@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 416 bytes --]

Hi all,

In commit

  de80166a573d ("aio: Fix io_pgetevents() struct __compat_aio_sigset layout")

Fixes tag

  Fixes: 7a074e96 ("aio: implement io_pgetevents")

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").

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

         reply	other threads:[~2019-10-21 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 21:07 linux-next: build warning after merge of the drm-misc-fixes tree Stephen Rothwell
2019-10-21 22:35 ` linux-next: build warning after merge of the vfs-fixes tree Stephen Rothwell
2019-10-21 20:44   ` Stephen Rothwell [this message]
2019-10-21 22:40     ` Guillem Jover
2019-11-10 22:09 linux-next: Fixes tag needs some work in " Stephen Rothwell
2020-11-12 21:02 Stephen Rothwell
2020-11-12 21:14 ` Al Viro
2021-03-25 20:51 Stephen Rothwell

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=20191022074426.2c0a2485@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=guillem@hadrons.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).