Re: [PATCH RFC 3/9] dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays

From: "Liu, Yujie" <yujie.liu@intel.com>
To: "chuck.lever@oracle.com" <chuck.lever@oracle.com>
Cc: "cel@kernel.org" <cel@kernel.org>,
	"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
	lkp <lkp@intel.com>
Subject: Re: [PATCH RFC 3/9] dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays
Date: Mon, 23 Oct 2023 02:43:39 +0000	[thread overview]
Message-ID: <4a2b50ebbe3704f20c516248806453f919726349.camel@intel.com> (raw)
In-Reply-To: <D61BB9F1-C4AC-4654-9F0D-8FB4F3A737ED@oracle.com>

Hi Chuck,

On Thu, 2023-10-19 at 23:21 +0000, Chuck Lever III wrote:
> 
> 
> > On Oct 19, 2023, at 5:38 PM, kernel test robot <lkp@intel.com> wrote:
> > 
> > Hi Chuck,
> > 
> > [This is a private test report for your RFC patch.]
> > kernel test robot noticed the following build warnings:
> > 
> > [auto build test WARNING on akpm-mm/mm-everything]
> > [also build test WARNING on rdma/for-next linus/master v6.6-rc6 next-20231019]
> > [cannot apply to joro-iommu/next]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> > And when submitting patch, we suggest to use '--base' as documented in
> > https://git-scm.com/docs/git-format-patch#_base_tree_information]
> > 
> > url:    https://github.com/intel-lab-lkp/linux/commits/Chuck-Lever/dma-debug-Fix-a-typo-in-a-debugging-eye-catcher/20231020-032859
> > base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> > patch link:    https://lore.kernel.org/r/169772915215.5232.10127407258544978465.stgit%40klimt.1015granger.net
> > patch subject: [PATCH RFC 3/9] dma-debug: Add dma_debug_ helpers for mapping bio_vec arrays
> > config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20231020/202310200545.ScAzFYdK-lkp@intel.com/config)
> > compiler: m68k-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231020/202310200545.ScAzFYdK-lkp@intel.com/reproduce)
> > 
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > > Reported-by: kernel test robot <lkp@intel.com>
> > > Closes: https://lore.kernel.org/oe-kbuild-all/202310200545.ScAzFYdK-lkp@intel.com/
> 
> Fwiw, this was an RFC series. Reviewers have already rejected
> this approach, so I won't be posting another version of this.
> 
> Is there a way to flush out the test pipeline so no more tests
> are run on the series?

Sorry we are not able to flush out this patch series from the bot after
the test was triggered. We are not sure if there will be follow-up
reports for this series, but the reports for RFC patches are sent to
you privately and won't go to the mailing list. Please kindly ignore
them if the series is obsolete. Sorry for any inconvenience.

Best Regards,
Yujie