From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kent Overstreet <kent.overstreet@linux.dev>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-mm@kvack.org, tech-board-discuss@lists.linux.dev
Subject: Re: [GIT PULL] bcachefs for 6.15, v2...
Date: Wed, 26 Mar 2025 16:46:21 -0400 [thread overview]
Message-ID: <5b02fcfedcd006d202d38e2ec16b477919264408.camel@HansenPartnership.com> (raw)
In-Reply-To: <wg47lanrvfqkqdospive4b3ymc5snuhqdygcle33q3cxudw3xl@rkllblbmre4v>
On Mon, 2025-03-24 at 14:56 -0400, Kent Overstreet wrote:
> The following changes since commit
> 1a2b74d0a2a46c219b25fdb0efcf9cd7f55cfe5e:
>
> bcachefs: fix build on 32 bit in get_random_u64_below() (2025-03-14
> 19:45:54 -0400)
>
> are available in the Git repository at:
>
> git://evilpiepirate.org/bcachefs.git tags/bcachefs-2025-03-24
>
> for you to fetch changes up to
> d8bdc8daac1d1b0a4efb1ecc69bef4eb4fc5e050:
>
> bcachefs: Kill unnecessary bch2_dev_usage_read() (2025-03-24
> 09:50:37 -0400)
>
> ----------------------------------------------------------------
> bcachefs updates for 6.15
I note that the controversial block changes that got NAK'd but which
you tried to put into your first pull request are now removed from this
v2 pull request, thanks.
I also thought it was time to state more formally what's been
circulating around a few maintainers as shared knowledge: any tree you
send a pull request for that includes changes outside of bcachefs won't
be accepted by Linus.
Regards,
James Bottomley
next parent reply other threads:[~2025-03-26 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <wg47lanrvfqkqdospive4b3ymc5snuhqdygcle33q3cxudw3xl@rkllblbmre4v>
2025-03-26 20:46 ` James Bottomley [this message]
2025-03-28 15:48 ` Kent Overstreet
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=5b02fcfedcd006d202d38e2ec16b477919264408.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tech-board-discuss@lists.linux.dev \
--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