From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sergey Lapin <slapin@ossfans.org>
Cc: linux-x25@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow LAPB users know which data were actually sent.
Date: Thu, 17 Mar 2011 23:55:32 +0000 [thread overview]
Message-ID: <20110317235532.44c0e202@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1300400422-8820-1-git-send-email-slapin@ossfans.org>
On Thu, 17 Mar 2011 18:20:22 -0400
Sergey Lapin <slapin@ossfans.org> wrote:
> Normally, when LAPB is transport layer for X.25 protocol,
> internal mechanics of X.25 knows wheather data were actually
> received by peer. But for non-X.25 protocols which use LAPB
> as data reliability layer, it is important to have some way
> to know what was actually sent, so we add transmit indication.
Looks sensible but your patch doesn't add a user for it so what is it
needed for ?
next prev parent reply other threads:[~2011-03-17 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 22:20 [PATCH] Allow LAPB users know which data were actually sent Sergey Lapin
2011-03-17 23:55 ` Alan Cox [this message]
2011-03-18 0:52 ` Sergey Lapin
2011-03-18 3:24 ` David Miller
2011-03-18 11:34 ` Alan Cox
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=20110317235532.44c0e202@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=slapin@ossfans.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