linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [GIT PULL] Btrfs fix for 6.6-rc7
@ 2023-10-17 15:34 David Sterba
  2023-10-19 15:12 ` David Sterba
  2023-10-19 16:09 ` pr-tracker-bot
  0 siblings, 2 replies; 4+ messages in thread
From: David Sterba @ 2023-10-17 15:34 UTC (permalink / raw)
  To: torvalds; +Cc: David Sterba, linux-btrfs, linux-kernel

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(-)

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [GIT PULL] Btrfs fix for 6.6-rc7
  2023-10-17 15:34 [GIT PULL] Btrfs fix for 6.6-rc7 David Sterba
@ 2023-10-19 15:12 ` David Sterba
  2023-10-19 16:06   ` Linus Torvalds
  2023-10-19 16:09 ` pr-tracker-bot
  1 sibling, 1 reply; 4+ messages in thread
From: David Sterba @ 2023-10-19 15:12 UTC (permalink / raw)
  To: torvalds; +Cc: David Sterba, linux-btrfs, linux-kernel

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/cover.1697555249.git.dsterba@suse.com/
https://lore.kernel.org/linux-btrfs/cover.1697555249.git.dsterba@suse.com/

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(-)

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [GIT PULL] Btrfs fix for 6.6-rc7
  2023-10-19 15:12 ` David Sterba
@ 2023-10-19 16:06   ` Linus Torvalds
  0 siblings, 0 replies; 4+ messages in thread
From: Linus Torvalds @ 2023-10-19 16:06 UTC (permalink / raw)
  To: dave, torvalds, David Sterba, linux-btrfs, linux-kernel

On Thu, 19 Oct 2023 at 08:12, David Sterba <dave@jikos.cz> 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/cover.1697555249.git.dsterba@suse.com/
> https://lore.kernel.org/linux-btrfs/cover.1697555249.git.dsterba@suse.com/

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [GIT PULL] Btrfs fix for 6.6-rc7
  2023-10-17 15:34 [GIT PULL] Btrfs fix for 6.6-rc7 David Sterba
  2023-10-19 15:12 ` David Sterba
@ 2023-10-19 16:09 ` pr-tracker-bot
  1 sibling, 0 replies; 4+ messages in thread
From: pr-tracker-bot @ 2023-10-19 16:09 UTC (permalink / raw)
  To: David Sterba; +Cc: torvalds, David Sterba, linux-btrfs, linux-kernel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-10-19 16:09 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-10-17 15:34 [GIT PULL] Btrfs fix for 6.6-rc7 David Sterba
2023-10-19 15:12 ` David Sterba
2023-10-19 16:06   ` Linus Torvalds
2023-10-19 16:09 ` pr-tracker-bot

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).