public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kent Overstreet <kent.overstreet@linux•dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tags needs some work in the bcachefs tree
Date: Mon, 26 Feb 2024 08:29:41 +1100	[thread overview]
Message-ID: <20240226082941.039719fb@canb.auug.org.au> (raw)

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

Hi all,

In commit

  277112ce9192 ("thread_with_file: Fix missing va_end()")

Fixes tag

  Fixes: https://lore.kernel.org/linux-bcachefs/202402131603.E953E2CF@keescook/T/#u

has these problem(s):

  - No SHA1 recognised

In commit

  a7b46148ed37 ("bcachefs: Check for subvolume children when deleting subvolumes")

Fixes tag

  Fixes: https://github.com/koverstreet/bcachefs/issues/634

has these problem(s):

  - No SHA1 recognised

Please use a "Closes" tag for these.

In commit

  b58b1b883b9b ("bcachefs: fix iov_iter count underflow on sub-block dio read")

Fixes tag

  Fixes:

has these problem(s):

  - No SHA1 recognised

In commit

  204f45140faa ("bcachefs: Fix BTREE_ITER_FILTER_SNAPSHOTS on inodes btree")

Fixes tag

  Fixes:

has these problem(s):

  - No SHA1 recognised

In commit

  04fee68dd99a ("bcachefs: Kill __GFP_NOFAIL in buffered read path")

Fixes tag

  Fixes:

has these problem(s):

  - No SHA1 recognised

In commit

  1f626223a0c8 ("bcachefs: fix backpointer_to_text() when dev does not exist")

Fixes tag

  Fixes:

has these problem(s):

  - No SHA1 recognised

Just remove the empty Fixes: tags (or fill them in - and change to Closes:
if necessary).



-- 
Cheers,
Stephen Rothwell

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

                 reply	other threads:[~2024-02-25 21:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240226082941.039719fb@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=kent.overstreet@linux$(echo .)dev \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox