The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: acme@conectiva.com.br
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv4: udp seq_file support: produce only one record per seq_show
Date: Tue, 15 Oct 2002 23:39:14 -0700 (PDT)	[thread overview]
Message-ID: <20021015.233914.68256249.davem@redhat.com> (raw)
In-Reply-To: <20021016062449.GC1352@conectiva.com.br>

   From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
   Date: Wed, 16 Oct 2002 03:24:49 -0300
   
   master.kernel.org:/home/acme/BK/net-2.5

Pulled.

Two notes:

1) ARP and FIB hacks need similar treatment
2) I don't think it's so nice to snprintf() onto the
   stack and then seq_printf() that in fib_node_seq_show.

   You should be able to keep the line within it's
   limit length just by specifying lengths to the integer
   formats.

Thanks.

  reply	other threads:[~2002-10-16  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16  6:24 [PATCH] ipv4: udp seq_file support: produce only one record per seq_show Arnaldo Carvalho de Melo
2002-10-16  6:39 ` David S. Miller [this message]
2002-10-16  6:49   ` 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=20021015.233914.68256249.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=acme@conectiva.com.br \
    --cc=kuznet@ms2.inr.ac.ru \
    --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