From: "Lin Ma" <linma@zju.edu.cn>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: wkang77@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH v1 1/2] staging: gdm724x: fix type confusion in gdm_lte_event_rcv()
Date: Thu, 3 Jul 2025 16:21:47 +0800 (GMT+08:00) [thread overview]
Message-ID: <1f0087d1.9735.197cf60a718.Coremail.linma@zju.edu.cn> (raw)
In-Reply-To: <2025070359-remold-aneurism-c0ac@gregkh>
>
> Ah, that was not obvious at all. Remember, some of us get thousands of
> emails a day to review, please make things that you are submitting for
> non-mainline kernels very very very obvious as to what is going on.
>
Gotcha, this is also the first time I encountered a bug that has been fixed
because it was "removed" (but not treated as a security issue) in upstream.
I will explain clearly what's happening and underline the non-mainline
information next time.
> > Therefore, shall I proceed with the patches? Or maybe the stable tree
> > could also delete that vulnerable code?
>
> For a staging driver, it's not an issue, don't worry about it, no distro
> should be using it anyway as no one has the hardware :)
>
Cool, glad to know that.
> thanks,
>
> greg k-h
Thanks
Lin
prev parent reply other threads:[~2025-07-03 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 5:27 [PATCH v1 1/2] staging: gdm724x: fix type confusion in gdm_lte_event_rcv() Lin Ma
2025-07-03 5:44 ` Greg KH
2025-07-03 6:29 ` Lin Ma
2025-07-03 6:45 ` Greg KH
2025-07-03 7:03 ` Lin Ma
2025-07-03 7:48 ` Greg KH
2025-07-03 8:21 ` Lin Ma [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=1f0087d1.9735.197cf60a718.Coremail.linma@zju.edu.cn \
--to=linma@zju.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=stable@kernel.org \
--cc=wkang77@gmail.com \
/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