All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <vladimir.kondratiev@intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	Alexander Viro <viro@math.psu.edu>
Subject: Re: PATCH: seq_file interface to provide large data chunks
Date: Thu, 10 Jul 2003 15:12:46 +0300	[thread overview]
Message-ID: <3F0D583E.8070307@intel.com> (raw)
In-Reply-To: <1057835373.8028.0.camel@dhcp22.swansea.linux.org.uk>

Alan,
I analyzed 2 latest patches from www.kernel.org:
patch-2.4.22-pre4 and patch-2.4.22-pre3-ac1.

-pre4 do not touch seq_file;

-pre3-ac1 corrects spelling and adds single_xxx functions. There is no 
conflict between this patch and my one. I verified, they do apply in any 
order (with some offset).

Vladimir.

Alan Cox wrote:

>On Iau, 2003-07-10 at 09:19, Vladimir Kondratiev wrote:
>  
>
>>seq_file interface, as it exist in last official kernel, never provides 
>>more then one page for each 'read' call. Old read_proc_t did loop to 
>>fill more than one page.
>>    
>>
>
>There is a merge of Al's additional seq_file stuff to 2.4 floating
>around (its in -ac for one) that may be a better thing to merge instead
>if we want it 
>
>Al ?
>
>  
>



  reply	other threads:[~2003-07-10 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10  8:19 PATCH: seq_file interface to provide large data chunks Vladimir Kondratiev
2003-07-10 11:09 ` Alan Cox
2003-07-10 12:12   ` Vladimir Kondratiev [this message]
2003-07-15 11:57   ` Vladimir Kondratiev
2003-07-11 15:13 ` Matt Mackall

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=3F0D583E.8070307@intel.com \
    --to=vladimir.kondratiev@intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=viro@math.psu.edu \
    /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.