On Mon, Apr 3, 2023 at 8:11 AM Dan Carpenter <error27@xxxxxxxxx> wrote: > > On Mon, Apr 03, 2023 at 07:05:56AM +0200, Sergio Paracuellos wrote: > > On Mon, Apr 3, 2023 at 6:41 AM Dan Carpenter <error27@xxxxxxxxx> wrote: > > > > > > Hi, > > > > > > https://git-scm.com/docs/git-format-patch#_base_tree_information] > > > > > > url: https://github.com/intel-lab-lkp/linux/commits/ye-xingchen-zte-com-cn/PCI-mt7621-Use-dev_err_probe/20230323-114623 > > > base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next > > > patch link: https://lore.kernel.org/r/202303231145121987818%40zte.com.cn > > > > So, I already replied to this proposed patch clearly saying that this > > makes the rest of the code unreachable, so it is a clear NAK. > > Why is this applied to the intel-lab-lkp tree? Just to be able to test > > the changes? > > > > These emails are automatically generated by kbuild-bot. I don't know > how kbuild-bot internals work. I just review some of the Smatch related > warnings and hit forward or ignore them. > > Normally, I don't look at the context outside of the email but to be > honest, I was curious enough about this one that I looked it up on the > list. I knew it was NAKed but I set the email anyway hoping that maybe > people would see the extra Smatch warning and be encouraged to run > Smatch on their code in the future to avoid potential embarrassment. I see :). Thanks for the explanation, Dan. Best regards, Sergio Paracuellos > > regards, > dan carpenter > >
