linux-kernel - Re: [PATCH] Allow LAPB users know which data were actually sent.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20110317.202419.189703451.davem@davemloft.net>
Date:	Thu, 17 Mar 2011 20:24:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	slapin@...fans.org
Cc:	alan@...rguk.ukuu.org.uk, linux-x25@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Allow LAPB users know which data were actually sent.

From: Sergey Lapin <slapin@...fans.org>
Date: Thu, 17 Mar 2011 20:52:20 -0400

> I implement accessor for special equipment (acessing fiscal information)
> which uses custom protocol over LAPB. As it is being implemented,
> I actually wanted to know if this approach for using LAPB is good enough
> for mainline submission, as I want to have kernel part to be in mainline.
> I think I will have the rest of patches ready within two weeks.

Submit the infrastructure for inclusion when you're user is completed
and submittable as well.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/