From: Benjamin LaHaise <ben@communityfibre.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: linux-mm@kvack.org - limping on a backup
Date: Fri, 25 Jun 2021 15:26:07 -0400 [thread overview]
Message-ID: <20210625192607.GH4058@kvack.org> (raw)
In-Reply-To: <6f309c63f5b7be968ae679e81ab959db05681e8a.camel@HansenPartnership.com>
On Fri, Jun 25, 2021 at 12:21:24PM -0700, James Bottomley wrote:
> On Fri, 2021-06-25 at 13:12 -0400, Benjamin LaHaise wrote:
> > On Fri, Jun 25, 2021 at 10:00:15AM -0700, James Bottomley wrote:
> > > Perhaps it's time to move this list over to vger or the linux.dev
> > > infrastructure now that it's being brought up? We already migrated
> > > the containers list without too much pain.
> >
> > Maybe the btrfs bugs should get fixed.
>
> I believe we can do both.
If I were unresponsive at fixing issues, I would understand the need to
migrate services, but steps to address the failures have already been
taken and additional mitigations are planned. If we migrated services
every time a piece of hardware failed or we hit a kernel bug, then we
wouldn't have any infrastructure left.
-ben
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2021-06-25 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 14:59 linux-mm@kvack.org - limping on a backup Benjamin LaHaise
2021-06-24 12:12 ` David Sterba
2021-06-25 17:00 ` James Bottomley
2021-06-25 17:12 ` Benjamin LaHaise
2021-06-25 19:21 ` James Bottomley
2021-06-25 19:26 ` Benjamin LaHaise [this message]
2021-06-25 21:52 ` James Bottomley
2021-06-28 13:46 ` Jason Gunthorpe
2021-06-28 13:53 ` Benjamin LaHaise
2021-06-28 14:26 ` Jason Gunthorpe
2021-06-28 14:40 ` Benjamin LaHaise
2021-06-28 16:20 ` Jason Gunthorpe
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=20210625192607.GH4058@kvack.org \
--to=ben@communityfibre.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.