[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13600e0c-bde2-198f-26c4-00531f277bf8@redhat.com>
Date: Sat, 20 Aug 2022 16:59:55 +0200
From: Hans de Goede <hdegoede@...hat.com>
To: Nam Cao <namcaov@...il.com>
Cc: lkp@...el.com, Larry.Finger@...inger.net,
gregkh@...uxfoundation.org, kbuild-all@...ts.01.org,
linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev
Subject: Re: [PATCH v2 0/4] remove useless files
Hi,
On 8/20/22 16:35, Nam Cao wrote:
> Hi
>
> On Sat, Aug 20, 2022 at 2:17 PM Hans de Goede <hdegoede@...hat.com> wrote:
>>
>> Hi,
>>
>> Patch 1/4 seems to be missing?
>
> Patch 1/4 is there:
> https://lore.kernel.org/linux-staging/46d73e331bae2192a328f6691763f39ea6c18b08.1660977536.git.namcaov@gmail.com/
>
>>
>> Also please squash patches 3 and 4:
>>
>> staging: rtl8723bs: remove odm_NoiseMonitor.o from Makefile
>> staging: rtl8723bs: remove odm_NoiseMonitor.h and odm_NoiseMonitor.c
>>
>> together. Ion other words remove both the files and the Makefile
>> target in a single patch please.
>
> Sorry but I am not sure what I am supposed to do with kernel test bot.
> I agree that it makes sense to squash these 2 commits together. However,
> I separated them because I want to have 1 patch addressing the problem reported
> by the bot, so that I can put the "Reported-by" line to this patch.
>
> If I squash them, should I still put in the "Reported-by" line, despite the
> commit not exactly fixing the reported error. Or should I just leave it out?
You should just leave it out, that is the standard thing to do for
bot reported problems which are fixed before the patches are merged.
Regards,
Hans
Powered by blists - more mailing lists