linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Eckenfels <ecki-news2002-09@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __KERNEL__ pasting in drivers/net/wan/cycx_x25.c
Date: Sat, 21 Sep 2002 14:29:28 +0200	[thread overview]
Message-ID: <E17sjO4-00008j-00@sites.inka.de> (raw)
In-Reply-To: <20020921112245.27021.qmail@unibar>

In article <20020921112245.27021.qmail@unibar> you wrote:
> This patch cleans up the __FUNCTION__ pasting to the new
> standard.

is this normal, that we dont have a rate limit in those functions? And even
worse, that there is no error handling like signalling this back to the
channel? In this case this looks especially annoying, since it is a state
changing event, if when lost may totally screw up the state engine (if i
understand the comment "Send event (connection, disconnection, etc) to X.25
socket layer" right.

Greetings
Bernd

      reply	other threads:[~2002-09-21 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-21 11:22 [PATCH] __KERNEL__ pasting in drivers/net/wan/cycx_x25.c adam
2002-09-21 12:29 ` Bernd Eckenfels [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=E17sjO4-00008j-00@sites.inka.de \
    --to=ecki-news2002-09@lina.inka.de \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).