From: Greg KH <gregkh@linuxfoundation.org>
To: 许红岩 <220255774@seu.edu.cn>
Cc: sashal <sashal@kernel.org>, 3chas3 <3chas3@gmail.com>,
stable <stable@vger.kernel.org>,
linux-atm-general <linux-atm-general@lists.sourceforge.net>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Re: [RFC PATCH 6.6.y] atm: he: kill tasklet before releasing queues
Date: Sun, 26 Jul 2026 14:50:55 +0200 [thread overview]
Message-ID: <2026072618-plank-game-15f5@gregkh> (raw)
In-Reply-To: <AIYAKgAhKje-OvrUBw*N1are.3.1785069041661.Hmail.220255774@seu.edu.cn>
On Sun, Jul 26, 2026 at 08:30:41PM +0800, 许红岩 wrote:
>
>
> Thanks greg k-h
> I do not have the HE hardware, so the patch has only been build-tested and
> reviewed against the teardown path.
Then why create these patches at all? What is driving the need for
them?
> Given that the driver has already been removed upstream, I agree that deleting
> it from maintained stable trees would be cleaner if that is acceptable for
> stable. I sent the small fix only because the driver is still present there
> and I did not want to backport the much larger ATM removal commit.
But if you don't have the hardware, and don't use this driver, why do
this at all? Why even look at older kernel versions for stuff that is
not used?
> I can prepare a stable-only removal patch for
> the HE driver instead, or backport the relevant upstream removal pieces if that
> is preferred.
As no one uses these drivers, due to lack of hardware and the like, they
can't be abused at all, so just leave them alone for older kernels, no
need to delete them as they do not cause any additional burden there at
all.
thanks,
greg k-h
prev parent reply other threads:[~2026-07-26 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 5:27 [RFC PATCH 6.6.y] atm: he: kill tasklet before releasing queues Hongyan Xu
2026-07-24 5:45 ` Greg KH
[not found] ` <AIYAKgAhKje-OvrUBw*N1are.3.1785069041661.Hmail.220255774@seu.edu.cn>
2026-07-26 12:50 ` Greg KH [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=2026072618-plank-game-15f5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=220255774@seu.edu.cn \
--cc=3chas3@gmail.com \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sashal@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