All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@redhat.com>
Cc: neilb@cse.unsw.edu.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv4: make arp seq_file show method only produce one record per call
Date: Wed, 16 Oct 2002 23:00:01 -0300	[thread overview]
Message-ID: <20021017020001.GV7541@conectiva.com.br> (raw)
In-Reply-To: <20021016.182814.23034875.davem@redhat.com>

Em Wed, Oct 16, 2002 at 06:28:14PM -0700, David S. Miller escreveu:
>    From: Neil Brown <neilb@cse.unsw.edu.au>
>    Date: Thu, 17 Oct 2002 11:30:43 +1000
>    
>    I use seq->private for private state for /proc/fs/nfs/exports.
>    It works nicely.
>    You need to define an 'open' the sets it up, and a 'release' to
>    tear it down, rather than doing it in start/stop.
>    See fs/nfsd/fnsctl.c:exports_open
> 
> Hmmm, Arnaldo? :-)

	I know that it works :-) I just refrained from using it because it is
not the designed purpose for this field, as per what the author stated to me,
so I didn't wanted to use in a way that could change under my feet in the
future when Al decided to do some change in seq_file.

	But if Al changes his mind and state that this is valid use, great,
I'll happily use it.

	See my other post with Al's comments.

- Arnaldo

  reply	other threads:[~2002-10-17  1:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  1:01 [PATCH] ipv4: make arp seq_file show method only produce one record per call Arnaldo Carvalho de Melo
2002-10-17  0:58 ` David S. Miller
2002-10-17  1:11   ` Arnaldo Carvalho de Melo
2002-10-17  1:15     ` David S. Miller
2002-10-17  1:30       ` Neil Brown
2002-10-17  1:28         ` David S. Miller
2002-10-17  2:00           ` Arnaldo Carvalho de Melo [this message]
2002-10-17  2:10             ` Arnaldo Carvalho de Melo
2002-10-17  2:23               ` Arnaldo Carvalho de Melo
2002-10-17  1:35       ` Arnaldo Carvalho de Melo

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=20021017020001.GV7541@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.