linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Stevenson <james@stev.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: ncorbic@sangoma.com, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wanrouter: fix stack usage
Date: Sun, 8 Jun 2003 01:59:03 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0306080158280.1776-100000@jlap.stev.org> (raw)
In-Reply-To: <20030607234510.GB8511@wohnheim.fh-wedel.de>


Hi

i am guessing it doesnt compile.

int err;
err -ENOBUFS; ????


-                       return -ENOBUFS;
+                       err -ENOBUFS;
+                       goto out;


On Sun, 8 Jun 2003, Jörn Engel wrote:

> Hi!
> 
> Another stack patch that grew old until it didn't apply anymore.  Any
> reasons why it has been ignore so far?
> 
> Jörn
> 
> 


  reply	other threads:[~2003-06-07 23:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-07 23:45 [PATCH] wanrouter: fix stack usage Jörn Engel
2003-06-08  0:59 ` James Stevenson [this message]
2003-06-08  0:10   ` Jörn Engel

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=Pine.LNX.4.44.0306080158280.1776-100000@jlap.stev.org \
    --to=james@stev.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncorbic@sangoma.com \
    /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).