All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher Snowhill" <chris@kode54.net>
To: "Malte Schröder" <malte.schroeder@tnxip.de>,
	"John Stoffel" <john@stoffel.org>,
	"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>
Subject: Re: [GIT PULL] bcachefs changes for 6.16
Date: Wed, 28 May 2025 03:00:38 -0700	[thread overview]
Message-ID: <DA7PG162QJME.2FUT6C3GBGDB3@kode54.net> (raw)
In-Reply-To: <c2001c69-e735-4976-ac8b-6269c825cb92@tnxip.de>

On Wed May 28, 2025 at 2:33 AM PDT, Malte Schröder wrote:
> On 28/05/2025 11:00, Christopher Snowhill wrote:
>> On Tue May 27, 2025 at 11:52 AM PDT, John Stoffel wrote:
>>>>>>>> "Kent" == Kent Overstreet <kent.overstreet@linux.dev> writes:
>>>> There was a feature request I forgot to mention - New option,
>>>> 'rebalance_on_ac_only'. Does exactly what the name suggests, quite
>>>> handy with background compression.
>>> LOL, only if you know what the _ac_ part stands for.  :-)
>> Would you have suggested perhaps _mains_ ? That may have rang better
>> with some folks. I suppose, at least.
>>
> What about 'no_rebalance_on_battery'? 

Oh, awesome suggestion. A little inversion of language, so battery is
front and center, and we avoid having to think of a billion different
terms for line power. What say anyone else?

>
> /Malte


  reply	other threads:[~2025-05-28 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25  0:47 [GIT PULL] bcachefs changes for 6.16 Kent Overstreet
2025-05-25  2:19 ` Kent Overstreet
2025-05-27 18:52   ` John Stoffel
2025-05-28  9:00     ` Christopher Snowhill
2025-05-28  9:33       ` Malte Schröder
2025-05-28 10:00         ` Christopher Snowhill [this message]
2025-05-26 21:20 ` 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=DA7PG162QJME.2FUT6C3GBGDB3@kode54.net \
    --to=chris@kode54.net \
    --cc=john@stoffel.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=malte.schroeder@tnxip.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.