From: Hongbo Li <lihongbo22@huawei.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: <bfoster@redhat.com>, <linux-bcachefs@vger.kernel.org>
Subject: Re: [PATCH RFC 0/2] bcachefs: refactoring of btree_path status
Date: Thu, 21 Mar 2024 10:00:42 +0800 [thread overview]
Message-ID: <0e7dcf73-e9de-4085-98be-b131b1ca5b93@huawei.com> (raw)
In-Reply-To: <6ji2r4vsxucyj6i6kfve2nwk5bmwozzevpr47jtnryzjb3ggrt@hyddohv2cia5>
Do you mean I provide my git repo? If so, what format should it be?
(such as ${repo_url}?branch=${branch_name}?).
On 2024/3/21 3:55, Kent Overstreet wrote:
> On Wed, Mar 20, 2024 at 03:43:44PM -0400, Kent Overstreet wrote:
>> On Wed, Mar 20, 2024 at 02:29:21PM +0800, Hongbo Li wrote:
>>> To enhance the code readability about btree_path structure, we did
>>> some refactoring on the relevant code based on my understanding.
>>>
>>> Hongbo Li (2):
>>> bcachefs: use btree_path_state to represent btree_path status
>>> bcachefs: optimize btree_path status representation
>>
>> you've got some things to look at here:
>>
>> https://evilpiepirate.org/~testdashboard/ci?branch=refactor-heap
>
> sorry, wrong thread, but post your git repo and I'll add you to the CI
prev parent reply other threads:[~2024-03-21 2:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 6:29 [PATCH RFC 0/2] bcachefs: refactoring of btree_path status Hongbo Li
2024-03-20 6:29 ` [PATCH RFC 1/2] bcachefs: use btree_path_state to represent " Hongbo Li
2024-03-20 17:39 ` Brian Foster
2024-03-20 19:57 ` Kent Overstreet
2024-03-20 20:10 ` Kent Overstreet
2024-03-20 6:29 ` [PATCH RFC 2/2] bcachefs: optimize btree_path status representation Hongbo Li
2024-03-20 17:41 ` Brian Foster
2024-03-20 20:50 ` Kent Overstreet
2024-03-21 1:53 ` Hongbo Li
2024-03-20 20:06 ` Kent Overstreet
2024-03-21 1:44 ` Hongbo Li
2024-03-20 19:43 ` [PATCH RFC 0/2] bcachefs: refactoring of btree_path status Kent Overstreet
2024-03-20 19:55 ` Kent Overstreet
2024-03-21 2:00 ` Hongbo Li [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=0e7dcf73-e9de-4085-98be-b131b1ca5b93@huawei.com \
--to=lihongbo22@huawei.com \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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 read-only IMAP folder(s) and NNTP newsgroup(s).