linux-kernel - RE: [PATCH char-misc-next] misc: microchip: pci1xxxx: Include depends on PCI & select AUXILIARY_BUS in the Kconfig file to resolve build issues.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 6 Sep 2022 10:51:27 +0000
From:   <Kumaravel.Thiagarajan@...rochip.com>
To:     <gregkh@...uxfoundation.org>
CC:     <linux-kernel@...r.kernel.org>, <kbuild-all@...ts.01.org>,
        <lkp@...el.com>
Subject: RE: [PATCH char-misc-next] misc: microchip: pci1xxxx: Include depends
 on PCI & select AUXILIARY_BUS  in the Kconfig file to resolve build issues.

> -----Original Message-----
> From: Greg KH <gregkh@...uxfoundation.org>
> Sent: Tuesday, September 6, 2022 2:19 PM
> To: Kumaravel Thiagarajan - I21417 <Kumaravel.Thiagarajan@...rochip.com>
> Cc: linux-kernel@...r.kernel.org; kbuild-all@...ts.01.org; lkp@...el.com
> Subject: Re: [PATCH char-misc-next] misc: microchip: pci1xxxx: Include
> depends on PCI & select AUXILIARY_BUS in the Kconfig file to resolve build
> issues.
> 
> 
> Your subject line is way too long :(
I have tried to make it a little shorter.

> 
> 
> On Tue, Sep 06, 2022 at 02:05:55PM +0530, Kumaravel Thiagarajan wrote:
> > Some build errors were reported by kernel test robot <lkp@...el.com>
> > on the char-misc-next branch. This add-on patch will fix the errors.
> 
> You should list the errors here so that we know what they are.
Ok. This is taken care of in v2.

> 
> >
> > Fixes: 393fc2f5948fd340d016a9557eea6e1ac2f6c60c
> 
> As per the kernel documentation, this should be:
> Fixes: 393fc2f5948f ("misc: microchip: pci1xxxx: load auxiliary bus driver for
> the PIO function in the multi-function endpoint of pci1xxxx device.")
Ok. This is taken care of in v2.

> 
> Can you fix this up and send a v2?
I have sent you the v2 but just now noticed that I did not include v1 -> V2 change history. I am really sorry about that.

Thank You.

Regards,
Kumaravel