linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: linux-next: Fixes tag needs some work in the xfs tree
Date: Fri, 17 Apr 2020 08:19:22 +1000	[thread overview]
Message-ID: <20200417081922.3b539711@canb.auug.org.au> (raw)

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

Hi all,

In commit

  63dc90feaa20 ("xfs: move inode flush to the sync workqueue")

Fixes tag

  Fixes: bdd4ee4f8407 ("xfs: ratelimit inode flush on buffered write ENOSPC")

has these problem(s):

  - Target SHA1 does not exist

Maybe you meant

Fixes: c6425702f21e ("xfs: ratelimit inode flush on buffered write ENOSPC")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-04-16 22:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 22:19 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-19  7:25 linux-next: Fixes tag needs some work in the xfs tree Stephen Rothwell
2023-06-05  4:22 Stephen Rothwell
2020-05-10 20:49 Stephen Rothwell
2019-12-19 20:48 Stephen Rothwell
2019-08-12 21:45 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=20200417081922.3b539711@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 \
    /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).