All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, david@rowetel.com
Subject: Re: users of drivers/misc/echo ?
Date: Tue, 25 Feb 2025 20:08:07 +0100	[thread overview]
Message-ID: <Z74VF1Uw5sRVbXhy@nataraja> (raw)
In-Reply-To: <Z74OSsZqeboJml9c@gallifrey>

Hi Dave,

On Tue, Feb 25, 2025 at 06:39:06PM +0000, Dr. David Alan Gilbert wrote:
> > Actually, looking at DAHDI, I really don't think anyone is still using
> > the dahdi_echocan_oslec code.  It is disabled by default and only built
> > if explicitly enabled by the user, and indeed if anyone did that it
> > would fail to build for any kernels that have moved it out of staging.
> 
> It looks like Debian is including and enabling it in it's DKMS build:

thanks, I didn't realize that.  You could reach out to the Debian maintainer of the package
if you'd want clarification.

-- 
- Harald Welte <laforge@gnumonks.org>          https://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

  parent reply	other threads:[~2025-02-25 19:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-23 17:23 users of drivers/misc/echo ? Dr. David Alan Gilbert
2025-02-23 20:38 ` Arnd Bergmann
2025-02-25 12:33   ` Harald Welte
2025-02-25 13:01     ` Dr. David Alan Gilbert
2025-02-25 13:58       ` Harald Welte
2025-02-25 18:39         ` Dr. David Alan Gilbert
2025-02-25 19:02           ` Arnd Bergmann
2025-02-25 19:08           ` Harald Welte [this message]
2025-02-25 22:04             ` Dr. David Alan Gilbert
2025-02-26  7:12               ` Harald Welte

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=Z74VF1Uw5sRVbXhy@nataraja \
    --to=laforge@gnumonks.org \
    --cc=arnd@arndb.de \
    --cc=david@rowetel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.