On 17/03/2025 09:51, Ryan Chen wrote: >> Subject: Re: [PATCH v16 2/3] i2c: aspeed: support AST2600 i2c new register >> mode driver >> >> On Mon, Mar 17, 2025 at 08:48:03AM +0100, Krzysztof Kozlowski wrote: >>> On 28/02/2025 13:38, Andy Shevchenko wrote: >>>> On Fri, Feb 28, 2025 at 09:28:59AM +0800, kernel test robot wrote: >>>>> Hi Ryan, >>>>> >>>>> kernel test robot noticed the following build warnings: >>>>> >>>>> [auto build test WARNING on andi-shyti/i2c/i2c-host] [also build >>>>> test WARNING on linus/master v6.14-rc4 next-20250227] [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/Ryan-Chen/dt-bindings-i2c-asp >> eed-support-for-AST2600-i2cv2/20250224-140221 >>>>> base: >> https://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git i2c/i2c-host >>>>> patch link: >> https://lore.kernel.org/r/20250224055936.1804279-3-ryan_chen%40aspeedtec >> h.com >>>>> patch subject: [PATCH v16 2/3] i2c: aspeed: support AST2600 i2c new >>>>> register mode driver >>>>> config: mips-allyesconfig >>>>> (https://download.01.org/0day-ci/archive/20250228/202502280902.U0gL >>>>> Dhve-lkp@xxxxxxxxx/config) >>>>> compiler: mips-linux-gcc (GCC) 14.2.0 reproduce (this is a W=1 >>>>> build): >>>>> (https://download.01.org/0day-ci/archive/20250228/202502280902.U0gL >>>>> Dhve-lkp@xxxxxxxxx/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@xxxxxxxxx> >>>>> | Closes: >>>>> | https://lore.kernel.org/oe-kbuild-all/202502280902.U0gLDhve-lkp@i >>>>> | ntel.com/ >>>>> >>>>> All warnings (new ones prefixed by >>): >>>> >>>> My gosh, this is valid report. But it looks like a preexisted issue. >>>> Can somebody fix this, please? >>> >>> >>> That was three weeks ago and still no responses from Aspeed or >>> contributors from here. >>> >>> I think this tells a lot about aspeedtech.com patchsets on the list. >> > Sorry, I don't aware this is my patches issue, could you tell me what build instruction can reproduce this? Everything is explained in the email. You do not need two people explaining the report, just read the report. Best regards, Krzysztof
