linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 208911] Renesas USB controller - FW has invalid version :8224
Date: Thu, 20 Aug 2020 07:14:37 +0000	[thread overview]
Message-ID: <bug-208911-208809-5BTEc6nJaq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208911-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=208911

--- Comment #11 from DocMAX (forum@docmax.my.to) ---
Also noticed this line when updating initramfs. Is this related?

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g
/boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.8.1-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keymap]
  -> Running build hook: [modconf]
  -> Running build hook: [block]

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-08-20  7:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-208911-208809@https.bugzilla.kernel.org/>
2020-08-15 17:06 ` [Bug 208911] Renesas USB controller - FW has invalid version :8224 bugzilla-daemon
2020-08-16  5:49 ` bugzilla-daemon
2020-08-17 10:55 ` bugzilla-daemon
2020-08-18  6:41 ` bugzilla-daemon
2020-08-20  7:14 ` bugzilla-daemon [this message]
2020-08-21  5:34 ` bugzilla-daemon
2020-08-21 22:05 ` bugzilla-daemon
2020-08-31  8:19 ` bugzilla-daemon
2020-09-16 21:13 ` bugzilla-daemon
2020-09-20 21:38 ` bugzilla-daemon
2020-09-21  5:05   ` Greg KH
2020-09-21  5:05 ` bugzilla-daemon
2020-09-21  7:26 ` bugzilla-daemon
2020-09-22  4:05 ` bugzilla-daemon
2020-10-05 16:42 ` 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=bug-208911-208809-5BTEc6nJaq@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).