From: Guillem Jover <guillem@hadrons.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: build warning after merge of the vfs-fixes tree
Date: Tue, 22 Oct 2019 00:40:57 +0200 [thread overview]
Message-ID: <20191021224057.GA6880@thunder.hadrons.org> (raw)
In-Reply-To: <20191022093512.4317a715@canb.auug.org.au> <20191022074426.2c0a2485@canb.auug.org.au>
Hi!
On Tue, 2019-10-22 at 07:44:26 +1100, Stephen Rothwell wrote:
> 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").
On Tue, 2019-10-22 at 09:35:12 +1100, Stephen Rothwell wrote:
> On Tue, 22 Oct 2019 08:07:34 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > fs/aio.c:2196:38: note: in expansion of macro 'NULL'
> > 2196 | struct __compat_aio_sigset ksig = { NULL, };
> > | ^~~~
> > fs/aio.c:2196:38: note: in expansion of macro 'NULL'
> > 2196 | struct __compat_aio_sigset ksig = { NULL, };
> > | ^~~~
> > fs/aio.c:2231:38: note: in expansion of macro 'NULL'
> > 2231 | struct __compat_aio_sigset ksig = { NULL, };
> > | ^~~~
> > fs/aio.c:2231:38: note: in expansion of macro 'NULL'
> > 2231 | struct __compat_aio_sigset ksig = { NULL, };
> > | ^~~~
> >
> > Introduced by commit
> >
> > de80166a573d ("aio: Fix io_pgetevents() struct __compat_aio_sigset layout")
Ugh, sorry about that, I guess I didn't see the warnings in the scroll
back when I built this back then for testing. :/ Sending a new version
fixing both issues.
Thanks,
Guillem
next prev parent reply other threads:[~2019-10-21 23:11 UTC|newest]
Thread overview: 5+ 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 ` linux-next: Fixes tag needs some work in " Stephen Rothwell
2019-10-21 22:40 ` Guillem Jover [this message]
2019-12-02 22:32 linux-next: build warning after merge of " 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=20191021224057.GA6880@thunder.hadrons.org \
--to=guillem@hadrons.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).