From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Subject: linux-next: Fixes tag needs some work in the xfs tree
Date: Tue, 13 Aug 2019 07:45:06 +1000 [thread overview]
Message-ID: <20190813074506.3e2ee2c8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
Hi all,
In commit
294fc7a4c8ec ("fs: xfs: xfs_log: Don't use KM_MAYFAIL at xfs_log_reserve().")
Fixes tag
Fixes: eb01c9cd87 ("[XFS] Remove the xlog_ticket allocator")
has these problem(s):
- SHA1 should be at least 12 digits long
This can be fixed for the future 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:[~2019-08-12 21:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 21:45 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-11 21:21 linux-next: Fixes tag needs some work in the xfs tree Stephen Rothwell
2025-02-11 22:31 ` Darrick J. Wong
2025-02-12 15:52 ` Carlos Maiolino
2024-10-08 20:06 Stephen Rothwell
2023-09-19 7:25 Stephen Rothwell
2023-06-05 4:22 Stephen Rothwell
2020-05-10 20:49 Stephen Rothwell
2020-04-16 22:19 Stephen Rothwell
2019-12-19 20:48 Stephen Rothwell
2019-01-29 20:56 Stephen Rothwell
2019-01-29 22:08 ` Dave Chinner
2019-01-29 23:06 ` Stephen Rothwell
2019-01-29 23:43 ` Dave Chinner
2019-01-30 0:02 ` Stephen Rothwell
2019-01-30 0:38 ` Dave Chinner
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=20190813074506.3e2ee2c8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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).