public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: kernel test robot <lkp@intel.com>, <axboe@kernel.dk>,
	<llvm@lists.linux.dev>, <oe-kbuild-all@lists.linux.dev>,
	<miklos@szeredi.hu>, <bschubert@ddn.com>,
	<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v1 8/9] fuse: add zero-copy over io-uring
Date: Tue, 31 Mar 2026 11:35:18 +0800	[thread overview]
Message-ID: <actA9on+WCPxpTXe@rli9-mobl> (raw)
In-Reply-To: <CAJnrk1Z=yMy3FSt7wvCDgGCr-NQD4M=na2sAGsRM=KoTH2Nazw@mail.gmail.com>

On Mon, Mar 30, 2026 at 08:43:16AM -0700, Joanne Koong wrote:
> On Sat, Mar 28, 2026 at 6:54 AM kernel test robot <lkp@intel.com> wrote:
> >
> > Hi Joanne,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on mszeredi-fuse/for-next]
> > [also build test ERROR on linus/master v7.0-rc5 next-20260327]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> 
> As noted in the cover letter, this series has a dependency on two
> prior patchsets submitted to the io-uring tree. This series is for the
> io-uring tree, not the fuse tree.

Thanks for the info, I will further check to see how to improve the bot as
so far, the bot can't accurately analyze the dependency from cover letter.

Sorry about the false positive.

> 
> Thanks,
> Joanne
> 

      reply	other threads:[~2026-03-31  3:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260324224532.3733468-9-joannelkoong@gmail.com>
2026-03-28 13:53 ` [PATCH v1 8/9] fuse: add zero-copy over io-uring kernel test robot
2026-03-30 15:43   ` Joanne Koong
2026-03-31  3:35     ` Philip 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=actA9on+WCPxpTXe@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=axboe@kernel.dk \
    --cc=bschubert@ddn.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=miklos@szeredi.hu \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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