From: Ming Qing <a0yami@mailbox.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Daniel Starke <daniel.starke@siemens.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] tty: n_gsm: pin DLCI during configuration ioctls
Date: Fri, 28 Aug 2026 16:22:59 +0800 (CST) [thread overview]
Message-ID: <2073007787.358333.1787905379172@app.mailbox.org> (raw)
In-Reply-To: <2026082810-vastness-detest-6637@gregkh>
> On 08/28/2026 1:50 PM CST Greg Kroah-Hartman wrote:
> Please have your llm read the email archives for why you shouldn't be
> touching this file at all, UNLESS you have the real hardware and system
> to test it with.
>
> thanks,
>
> greg k-h
Thanks for the reminder.
I'll be more careful with fixes like this in the future.
Best regards,
Qing Ming
prev parent reply other threads:[~2026-08-28 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 3:19 [PATCH] tty: n_gsm: pin DLCI during configuration ioctls Qing Ming
2026-08-28 3:37 ` sashiko-bot
2026-08-28 5:50 ` Greg Kroah-Hartman
2026-08-28 8:22 ` Ming Qing [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=2073007787.358333.1787905379172@app.mailbox.org \
--to=a0yami@mailbox.org \
--cc=daniel.starke@siemens.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=stable@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