From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Vitaly Chikunov <vt@altlinux•org>,
Arnaldo Carvalho de Melo <acme@redhat•com>
Subject: linux-next: Fixes tags need some work in the tip tree
Date: Thu, 16 Jan 2020 07:03:56 +1100 [thread overview]
Message-ID: <20200116070356.10b48388@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
Hi all,
In commit
6c4798d3f08b ("tools lib: Fix builds when glibc contains strlcpy()")
Fixes tag
Fixes: ce99091 ("perf tools: Move strlcpy() from perf to tools/lib/string.c")
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").
Fixes tag
Fixes: 0215d59 ("tools lib: Reinstate strlcpy() header guard with __UCLIBC__")
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 --]
next reply other threads:[~2020-01-15 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 20:03 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-21 22:31 linux-next: Fixes tags need some work in the tip tree Stephen Rothwell
2024-07-23 11:02 ` Marc Zyngier
2024-07-26 12:04 ` Thomas Gleixner
2021-03-08 2:16 Stephen Rothwell
2021-03-08 8:38 ` Ingo Molnar
2019-11-05 11:18 Stephen Rothwell
2019-11-05 11:52 ` Thomas Gleixner
2019-10-22 20:16 Stephen Rothwell
2019-10-22 20:30 ` Thomas Hellstrom
2019-10-23 10:16 ` Ingo Molnar
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=20200116070356.10b48388@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=acme@redhat$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=vt@altlinux$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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