From: Dave Chinner <david@fromorbit.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: Fixes tag needs some work in the xfs tree
Date: Wed, 30 Jan 2019 09:08:02 +1100 [thread overview]
Message-ID: <20190129220802.GC4205@dastard> (raw)
In-Reply-To: <20190130075647.53e86078@canb.auug.org.au>
On Wed, Jan 30, 2019 at 07:56:47AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 4ea899ead278 ("iomap: fix a use after free in iomap_dio_rw")
>
> Fixes tag
>
> Fixes: ff6a9292e6 ("iomap: implement direct I/O")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
Might be worth adding this to the boiler plate code:
This can be fixed by adding the following to your ~/.gitconfig file:
[core]
abbrev = 12
Thanks!
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-01-29 22:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 20:56 linux-next: Fixes tag needs some work in the xfs tree Stephen Rothwell
2019-01-29 22:08 ` Dave Chinner [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2019-08-12 21:45 Stephen Rothwell
2019-12-19 20:48 Stephen Rothwell
2020-04-16 22:19 Stephen Rothwell
2020-05-10 20:49 Stephen Rothwell
2023-06-05 4:22 Stephen Rothwell
2023-09-19 7:25 Stephen Rothwell
2024-10-08 20:06 Stephen Rothwell
2025-02-11 21:21 Stephen Rothwell
2025-02-11 22:31 ` Darrick J. Wong
2025-02-12 15:52 ` Carlos Maiolino
2025-12-17 21:06 Stephen Rothwell
2025-12-18 5:09 ` Christoph Hellwig
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=20190129220802.GC4205@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.