public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Yujie Liu <yujie.liu@intel.com>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: kernel test robot <lkp@intel.com>,
	linux-btrfs@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 3/4] btrfs: subpage: introduce helpers to handle subpage delalloc locking
Date: Tue, 20 Feb 2024 18:56:33 +1030	[thread overview]
Message-ID: <f4a2d37d-33fc-426d-975e-5408ada21710@suse.com> (raw)
In-Reply-To: <ZdRbi3gumI2fGhUq@yujie-X299>



在 2024/2/20 18:28, Yujie Liu 写道:
> Hi Qu,
> 
> On Tue, Feb 20, 2024 at 11:46:17AM +1030, Qu Wenruo wrote:
>> 在 2024/2/20 11:22, kernel test robot 写道:
>>> Hi Qu,
>>>
>>> kernel test robot noticed the following build errors:
>>>
>>> [auto build test ERROR on kdave/for-next]
>>> [also build test ERROR on linus/master v6.8-rc5 next-20240219]
>>> [If your patch is applied to the wrong git tree, kindly drop us a note.
>>
>> This is applied without the previous preparation patches.
>>
>> Is it possible to teach LKP to fetch from certain branch other than
>> applying them directly to for-next?
>>
>> Do I need certain keyword in the cover letter?
> 
> Sorry for applying this patchset on an incorrect base. If the cover
> letter mentions that the patches has already been pushed to a certain
> branch, usually we will skip the patchset and directly test that branch,
> but seems the bot didn't recognize that there is a github link in the
> cover letter. We will investigate this and fix it ASAP.

My guess is, I'm using github's branch URL in the cover letter:

   https://github.com/adam900710/linux/tree/subpage_delalloc

I guess I should go something more traditional like?

   https://github.com/adam900710/linux.git subpage_delalloc

Thanks,
Qu
> 
> Best Regards,
> Yujie

  reply	other threads:[~2024-02-20  8:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  6:08 [PATCH 0/4] btrfs: initial subpage support for zoned devices Qu Wenruo
2024-02-19  6:08 ` [PATCH 1/4] btrfs: make __extent_writepage_io() to write specified range only Qu Wenruo
2024-02-19  6:08 ` [PATCH 2/4] btrfs: lock subpage ranges in one go for writepage_delalloc() Qu Wenruo
2024-02-19  6:08 ` [PATCH 3/4] btrfs: subpage: introduce helpers to handle subpage delalloc locking Qu Wenruo
2024-02-20  0:52   ` kernel test robot
2024-02-20  1:16     ` Qu Wenruo
2024-02-20  7:58       ` Yujie Liu
2024-02-20  8:26         ` Qu Wenruo [this message]
2024-02-20  9:23           ` Yujie Liu
2024-02-19  6:08 ` [PATCH 4/4] btrfs: migrate writepage_delalloc() to use subpage helpers Qu Wenruo
2024-03-04  3:13 ` [PATCH 0/4] btrfs: initial subpage support for zoned devices Qu Wenruo
2024-03-04  5:10   ` Neal Gompa
2024-03-04  7:32     ` Qu Wenruo
2024-03-04 10:51       ` Neal Gompa

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=f4a2d37d-33fc-426d-975e-5408ada21710@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=yujie.liu@intel.com \
    /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