All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: bugzilla-daemon@kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 216020] New: drivers/usb/ folder compilation with allyesconfig fails
Date: Tue, 24 May 2022 17:07:40 +0200	[thread overview]
Message-ID: <Yoz0vGMOCDv1FlZc@kroah.com> (raw)
In-Reply-To: <bug-216020-208809@https.bugzilla.kernel.org/>

On Tue, May 24, 2022 at 02:58:45PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216020
> 
>             Bug ID: 216020
>            Summary: drivers/usb/ folder compilation with allyesconfig
>                     fails
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 5.18
>           Hardware: All
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: USB
>           Assignee: drivers_usb@kernel-bugs.kernel.org
>           Reporter: kushagra765@outlook.com
>         Regression: No
> 
> When compiling the drivers/usb/ folder with GCC version 12.1.0, the compilation
> fails with the following errors:

There are numerous errors when building the kernel with gcc 12.1 right
now.  It is being worked on, please see the development efforts on the
linux-kernel mailing list if you wish to help out.

Also, patches for this are always gladly accepted, no need to file a
bugzilla report for this.

thanks,

greg k-h

  reply	other threads:[~2022-05-24 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 14:58 [Bug 216020] New: drivers/usb/ folder compilation with allyesconfig fails bugzilla-daemon
2022-05-24 15:07 ` Greg KH [this message]
2022-05-24 15:07 ` [Bug 216020] " bugzilla-daemon
2022-05-24 15:16 ` bugzilla-daemon
2022-05-24 18:48 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yoz0vGMOCDv1FlZc@kroah.com \
    --to=greg@kroah.com \
    --cc=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.