From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: "Andreas Hindborg (Samsung)" <nmi@metaspace.dk>
Cc: Miguel Ojeda <ojeda@kernel.org>,
"Ariel Miculas (amiculas)" <amiculas@cisco.com>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>
Subject: Re: [RFC PATCH 00/80] Rust PuzzleFS filesystem driver
Date: Sat, 10 Jun 2023 11:32:22 +0200 [thread overview]
Message-ID: <CANiq72nrmZkTHgXSpeCeueSXeQ+oFfp89BZC0a_pRpMbb+txRw@mail.gmail.com> (raw)
In-Reply-To: <87r0qjisrd.fsf@metaspace.dk>
On Sat, Jun 10, 2023 at 11:14 AM Andreas Hindborg (Samsung)
<nmi@metaspace.dk> wrote:
>
> This is super annoying when it happens. What is the reason, are they too
> large? Miguel: can we do anything about this?
Yes as far as I know, and yes, you should Cc patches@lists.linux.dev,
if they are going to be big (I replied above about this [1] -- did you
receive it?).
[1] https://lore.kernel.org/rust-for-linux/CANiq72njK=6TYt1z8WBpRFhPJY=yVtxytxDUi=_Jtp1dZ3hKLQ@mail.gmail.com/
Cheers,
Miguel
next prev parent reply other threads:[~2023-06-10 9:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 7:19 [RFC PATCH 00/80] Rust PuzzleFS filesystem driver Ariel Miculas (amiculas)
2023-06-09 8:30 ` Miguel Ojeda
2023-06-09 8:40 ` Ariel Miculas (amiculas)
2023-06-10 9:11 ` Andreas Hindborg (Samsung)
2023-06-10 9:32 ` Miguel Ojeda [this message]
2023-06-10 10:24 ` Andreas Hindborg (Samsung)
2023-06-10 11:19 ` Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 6:29 Ariel Miculas
2023-06-09 10:26 ` Miguel Ojeda
2023-06-09 10:36 ` Christian Brauner
2023-06-09 11:42 ` Miguel Ojeda
[not found] ` <CH0PR11MB529981313ED5A1F815350E41CD51A@CH0PR11MB5299.namprd11.prod.outlook.com>
2023-06-09 11:45 ` Christian Brauner
2023-06-09 12:03 ` Ariel Miculas (amiculas)
2023-06-09 12:56 ` Gao Xiang
2023-06-09 12:07 ` Miguel Ojeda
2023-06-09 12:11 ` Ariel Miculas (amiculas)
2023-06-09 12:21 ` Greg KH
2023-06-09 13:05 ` Alice Ryhl
2023-06-09 12:20 ` Colin Walters
2023-06-09 12:42 ` Christian Brauner
2023-06-09 17:28 ` Serge Hallyn
2023-06-09 13:45 ` Ariel Miculas (amiculas)
2023-06-09 17:10 ` Trilok Soni
2023-06-09 17:16 ` Ariel Miculas (amiculas)
2023-06-09 17:41 ` Miguel Ojeda
2023-06-09 18:49 ` James Bottomley
2023-06-09 19:08 ` Miguel Ojeda
2023-06-09 19:11 ` Ariel Miculas
2023-06-09 20:01 ` James Bottomley
2023-06-10 9:34 ` Miguel Ojeda
2023-06-09 18:43 ` James Bottomley
2023-06-09 18:59 ` Ariel Miculas (amiculas)
2023-06-09 19:20 ` Ariel Miculas
2023-06-09 19:45 ` Trilok Soni
2023-06-09 19:53 ` Alice Ryhl
2023-06-09 23:52 ` Kent Overstreet
2023-06-10 9:40 ` Miguel Ojeda
2023-06-10 0:09 ` 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=CANiq72nrmZkTHgXSpeCeueSXeQ+oFfp89BZC0a_pRpMbb+txRw@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=amiculas@cisco.com \
--cc=nmi@metaspace.dk \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).