From: Randy Dunlap <rdunlap@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Theodore Ts'o <tytso@mit.edu>,
Kent Overstreet <kent.overstreet@linux.dev>
Cc: Greg KH <greg@kroah.com>, Mark Brown <broonie@kernel.org>,
Neal Gompa <neal@gompa.dev>, Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Nikolai Kondrashov <spbnick@gmail.com>,
Philip Li <philip.li@intel.com>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [GIT PULL] bcachefs updates for 6.8
Date: Wed, 17 Jan 2024 21:35:15 -0800 [thread overview]
Message-ID: <34862fc1-1cd9-47e3-b8e1-3fcce6ff7cf7@infradead.org> (raw)
In-Reply-To: <5b7154f86913a0957e0518b54365a1b0fce5fbea.camel@HansenPartnership.com>
On 1/17/24 05:03, James Bottomley wrote:
> Finally testing infrastructure is how OSDL (the precursor to the Linux
> foundation) got started and got its initial funding, so corporations
> have been putting money into it for decades with not much return (and
> pretty much nothing to show for a unified testing infrastructure ...
> ten points to the team who can actually name the test infrastructure
> OSDL produced) and have finally concluded it's not worth it, making it
> a 10x harder sell now.
What will ten points get me? a weak cup of coffee?
Do I need a team to answer the question?
Anyway, Crucible.
--
#Randy
next prev parent reply other threads:[~2024-01-18 5:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 19:36 [GIT PULL] bcachefs updates for 6.8 Kent Overstreet
2024-01-10 23:48 ` Kees Cook
2024-01-11 0:04 ` Kent Overstreet
2024-01-11 0:39 ` Kees Cook
2024-01-11 0:58 ` Kent Overstreet
2024-01-11 1:47 ` Linus Torvalds
2024-01-11 22:57 ` Matthew Wilcox
2024-01-11 23:42 ` Kees Cook
2024-01-11 23:58 ` Linus Torvalds
2024-01-12 0:05 ` Kent Overstreet
2024-01-12 0:18 ` Kees Cook
2024-01-11 15:35 ` Mark Brown
2024-01-11 17:38 ` Kent Overstreet
2024-01-11 21:47 ` Mark Brown
2024-01-12 1:10 ` Kent Overstreet
2024-01-12 11:11 ` Neal Gompa
2024-01-12 18:22 ` Mark Brown
2024-01-15 18:42 ` Kent Overstreet
2024-01-15 20:13 ` Greg KH
2024-01-17 4:41 ` Kent Overstreet
2024-01-17 5:31 ` Greg KH
2024-01-17 5:54 ` Theodore Ts'o
2024-01-17 13:03 ` James Bottomley
2024-01-17 18:19 ` Mark Brown
2024-01-21 3:24 ` Kent Overstreet
2024-01-25 21:46 ` Mark Brown
2024-01-18 2:49 ` Theodore Ts'o
2024-01-21 12:20 ` Kent Overstreet
2024-01-24 5:52 ` Theodore Ts'o
2024-01-18 5:35 ` Randy Dunlap [this message]
2024-01-21 2:49 ` Kent Overstreet
2024-01-17 17:33 ` Mark Brown
2024-01-11 2:23 ` 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=34862fc1-1cd9-47e3-b8e1-3fcce6ff7cf7@infradead.org \
--to=rdunlap@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=neal@gompa.dev \
--cc=philip.li@intel.com \
--cc=spbnick@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).