Hi,
please pull a "one-liner and thousand words", fixing a bug in chunk
size decision that could lead to suboptimal placement and filling
patterns. Thanks.
----------------------------------------------------------------
The following changes since commit 75f5f60bf7ee075ed4a29637ce390898b4c36811:
btrfs: add __counted_by for struct btrfs_delayed_item and use struct_size() (2023-10-11 11:37:19 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.6-rc6-tag
for you to fetch changes up to 8a540e990d7da36813cb71a4a422712bfba448a4:
btrfs: fix stripe length calculation for non-zoned data chunk allocation (2023-10-15 19:00:59 +0200)
----------------------------------------------------------------
Zygo Blaxell (1):
btrfs: fix stripe length calculation for non-zoned data chunk allocation
fs/btrfs/volumes.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi,
I don't see this pull request merged after 2 days and I don't see any
reply from you that there would be any problem.
The mail is in lore archives
https://lore.kernel.org/all/[email protected]/
https://lore.kernel.org/linux-btrfs/[email protected]/
what's a bit suspicious is the "X-Spamd-Bar: +++++++++++++++" header in
the raw message, this could explain it. Please let me know how to
proceed, thanks.
On Tue, Oct 17, 2023 at 05:34:56PM +0200, David Sterba wrote:
> Hi,
>
> please pull a "one-liner and thousand words", fixing a bug in chunk
> size decision that could lead to suboptimal placement and filling
> patterns. Thanks.
>
> ----------------------------------------------------------------
> The following changes since commit 75f5f60bf7ee075ed4a29637ce390898b4c36811:
>
> btrfs: add __counted_by for struct btrfs_delayed_item and use struct_size() (2023-10-11 11:37:19 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.6-rc6-tag
>
> for you to fetch changes up to 8a540e990d7da36813cb71a4a422712bfba448a4:
>
> btrfs: fix stripe length calculation for non-zoned data chunk allocation (2023-10-15 19:00:59 +0200)
>
> ----------------------------------------------------------------
> Zygo Blaxell (1):
> btrfs: fix stripe length calculation for non-zoned data chunk allocation
>
> fs/btrfs/volumes.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
On Thu, 19 Oct 2023 at 08:12, David Sterba <[email protected]> wrote:
>
> I don't see this pull request merged after 2 days and I don't see any
> reply from you that there would be any problem.
Indeed, I don't see the original in my mailbox, so re-sending it was
most definitely the right thing to do.
> The mail is in lore archives
> https://lore.kernel.org/all/[email protected]/
> https://lore.kernel.org/linux-btrfs/[email protected]/
Usually it goes the other way, where I see emails in my mailbox, but
not in lore.
I do check my spambox daily too, but honestly, it's a "quick scan" not
some deeper thing. So might have gotten deleted if it didn't stand out
to me clearly enough.
> what's a bit suspicious is the "X-Spamd-Bar: +++++++++++++++" header in
> the raw message, this could explain it. Please let me know how to
> proceed, thanks.
This was the right way - re-send in a couple of days if you feel like
things aren't moving along as they should and normally do.
Obviously the first merge window week is different - at that point it
can take me a few days just to get to it - so then "two days" might be
more like "four or five days".
Linus
The pull request you sent on Tue, 17 Oct 2023 17:34:56 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.6-rc6-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7cf4bea77ab60742c128c2ceb4b1b8078887b823
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html