From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
falemi@asu.edu, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] platform_get_irq_byname_optional -- dwc3-haps registers IRQ 0, WARN on first gadget init
Date: Fri, 28 Aug 2026 08:32:48 +0200 [thread overview]
Message-ID: <2026082806-irate-popper-0ce1@gregkh> (raw)
In-Reply-To: <CA+0ovChEnx=kEPqK025rVH9EXRBk-dvSTts8+2ufw6bmt7nrvg@mail.gmail.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Aug 27, 2026 at 11:16:24PM -0700, Farhad Alemi wrote:
> Greg,
>
> You're right; sorry. I've stopped sending.
>
> I'll resend individually, with the reproducer inline, and a proposed fix where I
> can write one. If you'd rather prefer that these not go to
> the lists at all, say so and I'll drop it.
We always want bugfixes, always send those. But random "here's a kernel
splat" with no information as to what you were doing to cause this, nor
any help in determining if it even is valid or not, is not helpful to
anyone, least of all yourself.
See how syzbot works and emulate that, as it seems like you are doing
almost the same exact thing.
good luck!
greg k-h
prev parent reply other threads:[~2026-08-28 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 5:34 [BUG] platform_get_irq_byname_optional -- dwc3-haps registers IRQ 0, WARN on first gadget init Farhad Alemi
2026-08-28 5:45 ` Greg Kroah-Hartman
2026-08-28 6:12 ` Greg Kroah-Hartman
2026-08-28 6:16 ` Farhad Alemi
2026-08-28 6:32 ` Greg Kroah-Hartman [this message]
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=2026082806-irate-popper-0ce1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=linux-kernel@vger.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