From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219951] Missing null check in ast_vhub_init_dev
Date: Sat, 29 Mar 2025 00:32:44 +0000 [thread overview]
Message-ID: <bug-219951-208809-fXMQxG1Kde@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219951-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219951
--- Comment #5 from henry (bsdhenrymartin@gmail.com) ---
Thank you for your feedback. I've now properly submitted this patch via
email to the relevant mailing lists with you in CC, as required by the
kernel submission process.
Please let me know if there are any issues with the submission format or
content that I should address. I'm happy to make any necessary adjustments.
<bugzilla-daemon@kernel.org> 于2025年3月29日周六 05:08写道:
> https://bugzilla.kernel.org/show_bug.cgi?id=219951
>
> --- Comment #4 from Greg Kroah-Hartman (greg@kroah.com) ---
> On Fri, Mar 28, 2025 at 01:14:23PM +0000, bugzilla-daemon@kernel.org
> wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=219951
> >
> > --- Comment #3 from henry (bsdhenrymartin@gmail.com) ---
> > This is patch file.
>
> Please read the kernel documentation for how to submit a patch in a way
> we can accept it. We can't take it through bugzilla, sorry.
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You reported the bug.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-03-29 0:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 11:15 [Bug 219951] New: Missing null check in ast_vhub_init_dev bugzilla-daemon
2025-03-28 11:27 ` Greg KH
2025-03-28 11:27 ` [Bug 219951] " bugzilla-daemon
2025-03-28 12:41 ` bugzilla-daemon
2025-03-28 13:14 ` bugzilla-daemon
2025-03-28 21:06 ` Greg KH
2025-03-28 21:08 ` bugzilla-daemon
2025-03-29 0:32 ` bugzilla-daemon [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=bug-219951-208809-fXMQxG1Kde@https.bugzilla.kernel.org/ \
--to=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 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).