From: 'Greg KH' <gregkh@linuxfoundation.org>
To: David Laight <David.Laight@aculab.com>
Cc: "t.martitz@avm.de" <t.martitz@avm.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: proc_lseek backport request
Date: Thu, 17 Aug 2023 17:59:58 +0200 [thread overview]
Message-ID: <2023081729-strained-hatchback-41af@gregkh> (raw)
In-Reply-To: <f98cf66371de47e6a0e87c5214ba2c22@AcuMS.aculab.com>
On Thu, Aug 17, 2023 at 03:42:02PM +0000, David Laight wrote:
> > Attempting to keep kernel code outside of the kernel tree is, on
> > purpose, very expensive in time and resources. The very simple way to
> > solve this is to get your drivers merged properly into the mainline
> > kernel tree.
>
> I've got some of those, you really wouldn't want them.
I would argue we do, but if you want to spend the extra time and money
keeping them out of the kernel, that's your choice to make.
> They are audio/telephony drivers for some very specific hardware.
As are almost all drivers in the kernel. Your hardware is special and
unique, just like all others :)
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-17 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 9:22 proc_lseek backport request t.martitz
2023-08-17 14:43 ` Greg KH
2023-08-17 15:42 ` David Laight
2023-08-17 15:59 ` 'Greg KH' [this message]
2023-08-21 6:28 ` t.martitz
2023-08-21 13:17 ` Greg KH
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=2023081729-strained-hatchback-41af@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@aculab.com \
--cc=stable@vger.kernel.org \
--cc=t.martitz@avm.de \
--cc=viro@zeniv.linux.org.uk \
/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