linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/3] docs: remove mention of "crc" cpio format support
Date: Fri, 11 Jun 2021 00:17:09 +0200	[thread overview]
Message-ID: <20210611001709.46ea8210@suse.de> (raw)
In-Reply-To: <YMKLs8kgUbz2oSdp@casper.infradead.org>

On Thu, 10 Jun 2021 23:01:23 +0100, Matthew Wilcox wrote:

> >  In human terms, the initramfs buffer contains a collection of
> > -compressed and/or uncompressed cpio archives (in the "newc" or "crc"
> > -formats); arbitrary amounts zero bytes (for padding) can be added
> > -between members.
> > +compressed and/or uncompressed cpio archives (in the "newc" format);
> > +arbitrary amounts zero bytes (for padding) can be added between
> > +members.  
> 
> "arbitrary amounts of zero bytes", but even that doesn't sound quite
> right.  Maybe "arbitrary amount of zero-byte padding between members"?

Your suggestion sounds good to me. Can I squash it in with this change
for a v2, or would you prefer to handle it as a separate grammar fix?

Cheers, David

      reply	other threads:[~2021-06-10 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 21:45 [PATCH 1/3] initramfs: move unnecessary memcmp from hot path David Disseldorp
2021-06-10 21:45 ` [PATCH 2/3] initramfs: print helpful cpio error on "crc" magic David Disseldorp
2021-06-10 21:45 ` [PATCH 3/3] docs: remove mention of "crc" cpio format support David Disseldorp
2021-06-10 22:01   ` Matthew Wilcox
2021-06-10 22:17     ` David Disseldorp [this message]

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=20210611001709.46ea8210@suse.de \
    --to=ddiss@suse.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=willy@infradead.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).