From: Sasha Levin <sashal@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, kees@kernel.org, hch@infradead.org,
broonie@kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.12-rc5
Date: Tue, 22 Oct 2024 15:06:38 -0400 [thread overview]
Message-ID: <Zxf3vp82MfPTWNLx@sashalap> (raw)
In-Reply-To: <rdjwihb4vl62psonhbowazcd6tsv7jp6wbfkku76ze3m3uaxt3@nfe3ywdphf52>
On Tue, Oct 22, 2024 at 01:39:10PM -0400, Kent Overstreet wrote:
>
>The following changes since commit 5e3b72324d32629fa013f86657308f3dbc1115e1:
>
> bcachefs: Fix sysfs warning in fstests generic/730,731 (2024-10-14 05:43:01 -0400)
>
>are available in the Git repository at:
>
> https://github.com/koverstreet/bcachefs tags/bcachefs-2024-10-22
Hi Linus,
There was a sub-thread on the linus-next discussion around improving
telemetry around -next/lore w.r.t soaking time and mailing list reviews
(https://lore.kernel.org/all/792F4759-EA33-48B8-9AD0-FA14FA69E86E@kernel.org/).
I've prototyped a set of scripts based on suggestions in the thread, and
wanted to see if you'd find it useful. A great way to test it out is with
a random pull request you'd review anyway :)
Is the below useful in any way? Or do you already do something like this
locally and I'm just wasting your time?
If it's useful, is bot reply to PRs the best way to share this? Any
other information that would be useful?
Here it goes:
Days in -next:
----------------------------------------
0 | ███████████ (5)
1 |
2 | █████████████████████████████████████████████████ (21)
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14+ |
Commits that didn't spend time in -next:
--------------------
a069f014797fd bcachefs: Set bch_inode_unpacked.bi_snapshot in old inode path
e04ee8608914d bcachefs: Mark more errors as AUTOFIX
f0d3302073e60 bcachefs: Workaround for kvmalloc() not supporting > INT_MAX allocations
3956ff8bc2f39 bcachefs: Don't use wait_event_interruptible() in recovery
eb5db64c45709 bcachefs: Fix __bch2_fsck_err() warning
Commits that weren't found on lore.kernel.org/all:
--------------------
e04ee8608914d bcachefs: Mark more errors as AUTOFIX
f0d3302073e60 bcachefs: Workaround for kvmalloc() not supporting > INT_MAX allocations
bc6d2d10418e1 bcachefs: fsck: Improve hash_check_key()
dc96656b20eb6 bcachefs: bch2_hash_set_or_get_in_snapshot()
15a3836c8ed7b bcachefs: Repair mismatches in inode hash seed, type
d8e879377ffb3 bcachefs: Add hash seed, type to inode_to_text()
78cf0ae636a55 bcachefs: INODE_STR_HASH() for bch_inode_unpacked
b96f8cd3870a1 bcachefs: Run in-kernel offline fsck without ratelimit errors
4007bbb203a0c bcachefS: ec: fix data type on stripe deletion
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-10-22 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 17:39 [GIT PULL] bcachefs fixes for 6.12-rc5 Kent Overstreet
2024-10-22 19:06 ` Sasha Levin [this message]
2024-10-22 19:30 ` Kees Cook
2024-10-22 19:34 ` Mark Brown
2024-10-23 11:39 ` Sasha Levin
2024-10-22 20:49 ` Darrick J. Wong
2024-10-22 21:20 ` Sasha Levin
2024-10-23 10:42 ` Michael Ellerman
2024-10-23 11:41 ` Sasha Levin
2024-10-24 22:19 ` Kent Overstreet
2024-10-22 22:58 ` Kent Overstreet
2024-10-24 20:33 ` pr-tracker-bot
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=Zxf3vp82MfPTWNLx@sashalap \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=hch@infradead.org \
--cc=kees@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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