linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-mm@kvack.org,
	linux-bcachefs@vger.kernel.org, viro@zeniv.linux.org.uk,
	akpm@linux-foundation.org, boqun.feng@gmail.com,
	brauner@kernel.org, hch@infradead.org, colyli@suse.de,
	djwong@kernel.org, mingo@redhat.com, jack@suse.cz,
	axboe@kernel.dk, willy@infradead.org, ojeda@kernel.org,
	ming.lei@redhat.com, ndesaulniers@google.com,
	peterz@infradead.org, phillip@squashfs.org.uk, urezki@gmail.com,
	longman@redhat.com, will@kernel.org
Subject: Re: [PATCH 00/32] bcachefs - a new COW filesystem
Date: Thu, 15 Jun 2023 22:41:56 +0200	[thread overview]
Message-ID: <20230615204156.GA1119@bug> (raw)
In-Reply-To: <20230509165657.1735798-1-kent.overstreet@linux.dev>

Hi!

> I'm submitting the bcachefs filesystem for review and inclusion.
> 
> Included in this patch series are all the non fs/bcachefs/ patches. The
> entire tree, based on v6.3, may be found at:
> 
>   http://evilpiepirate.org/git/bcachefs.git bcachefs-for-upstream
> 
> ----------------------------------------------------------------
> 
> bcachefs overview, status:
> 
> Features:
>  - too many to list
> 
> Known bugs:
>  - too many to list


Documentation: missing.

Dunno. I guess it would help review if feature and known bugs lists were included.

BR,
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2023-06-15 20:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 16:56 [PATCH 00/32] bcachefs - a new COW filesystem Kent Overstreet
2023-05-09 16:56 ` [PATCH 09/32] block: Add some exports for bcachefs Kent Overstreet
2023-05-09 16:56 ` [PATCH 10/32] block: Allow bio_iov_iter_get_pages() with bio->bi_bdev unset Kent Overstreet
2023-05-09 16:56 ` [PATCH 11/32] block: Bring back zero_fill_bio_iter Kent Overstreet
2023-05-09 16:56 ` [PATCH 12/32] block: Rework bio_for_each_segment_all() Kent Overstreet
2023-05-09 16:56 ` [PATCH 13/32] block: Rework bio_for_each_folio_all() Kent Overstreet
2023-06-15 20:41 ` Pavel Machek [this message]
2023-06-15 21:26   ` [PATCH 00/32] bcachefs - a new COW filesystem Kent Overstreet
  -- strict thread matches above, loose matches on Subject: below --
2023-05-15 11:15 Askar Safin

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=20230615204156.GA1119@bug \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=boqun.feng@gmail.com \
    --cc=brauner@kernel.org \
    --cc=colyli@suse.de \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=longman@redhat.com \
    --cc=ming.lei@redhat.com \
    --cc=mingo@redhat.com \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@kernel.org \
    --cc=peterz@infradead.org \
    --cc=phillip@squashfs.org.uk \
    --cc=urezki@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=will@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).