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: Fri, 18 Mar 2011 11:34:33 +0000 [thread overview]
Message-ID: <20110318113433.39794ca5@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20110318005220.GA9674@build.ihdev.net>
> > Looks sensible but your patch doesn't add a user for it so what is it
> > needed for ?
>
> 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.
It seems sensible as an implementation to me so I would carry on using
that model and then submit it with all the other bits when you are ready.
prev parent reply other threads:[~2011-03-18 11:34 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
2011-03-18 0:52 ` Sergey Lapin
2011-03-18 3:24 ` David Miller
2011-03-18 11:34 ` Alan Cox [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=20110318113433.39794ca5@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