netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: xemul@openvz.org
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2][KEY]: Convert net/pfkey to use seq files.
Date: Sat, 09 Feb 2008 23:21:01 -0800 (PST)	[thread overview]
Message-ID: <20080209.232101.94186105.davem@davemloft.net> (raw)
In-Reply-To: <47AC478E.3070507@openvz.org>

From: Pavel Emelyanov <xemul@openvz.org>
Date: Fri, 08 Feb 2008 15:14:06 +0300

> The seq files API disposes the caller of the difficulty of
> checking file position, the length of data to produce and
> the size of provided buffer.
> 
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>

Applied, but this kind of stuff is borderline wrt. the
"no new features" declaration.

Please queue future instances of this kind of stuff for when I open up
net-2.6.26, thanks.

      reply	other threads:[~2008-02-10  7:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 12:14 [PATCH 2/2][KEY]: Convert net/pfkey to use seq files Pavel Emelyanov
2008-02-10  7:21 ` David Miller [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=20080209.232101.94186105.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=xemul@openvz.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).