From: Anand Jain <anand.jain@oracle.com>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] fstests: btrfs changes staged-20240414
Date: Sun, 14 Apr 2024 20:31:57 +0800 [thread overview]
Message-ID: <be6e14ca-fbb6-46fe-81e4-dcbe23fa18a4@oracle.com> (raw)
In-Reply-To: <20240414070848.cpr4micelcs24qsw@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On 4/14/24 15:08, Zorro Lang wrote:
> On Sun, Apr 14, 2024 at 09:12:02AM +0800, Anand Jain wrote:
>> Please pull this branch containing changes as below.
>> These patches are on top of my last PR branch staged-20240403.
>>
>> Thank you.
>>
>> The following changes since commit 8aab1f1663031cccb326ffbcb087b81bfb629df8:
>>
>> common/btrfs: lookup running processes using pgrep (2024-04-03 15:09:01 +0800)
>>
>> are available in the Git repository at:
>>
>> https://github.com/asj/fstests.git staged-20240414
>
> Hi Anand,
>
> I've nearly done the upcoming fstests release of this weekend, I generally start
> my testing jobs on Friday night, and done on Sunday. So, sorry, this PR missed
> this merge window, I'll push them in next release if you don't mind. Or if some
> patches are hurry to be merged, I can increase an extra release in the middle of
> next week.
Yeah, this set, and another one in the ML, are larger changes which
almost touch most of the files. It will be better if we could get
both of these sets out as early as possible so that the next patch
being submitted, if any, will have fewer conflicts to fix. Plus, the
CI test cycles will be clearer. I'll submit another PR by midweek.
Thanks, Anand
prev parent reply other threads:[~2024-04-14 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 1:12 [GIT PULL] fstests: btrfs changes staged-20240414 Anand Jain
2024-04-14 7:08 ` Zorro Lang
2024-04-14 12:31 ` Anand Jain [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=be6e14ca-fbb6-46fe-81e4-dcbe23fa18a4@oracle.com \
--to=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=zlang@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).