From: Christoph Hellwig <hch@infradead.org>
To: Steve Whitehouse <Steve@ChyGwyn.com>
Cc: "David S. Miller" <davem@redhat.com>,
linux-decnet-user@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Remains of seq_file conversion for DECnet, plus fixes
Date: Thu, 1 May 2003 21:57:09 +0100 [thread overview]
Message-ID: <20030501215709.A28210@infradead.org> (raw)
In-Reply-To: <200305012052.VAA19274@gw.chygwyn.com>; from steve@gw.chygwyn.com on Thu, May 01, 2003 at 09:52:01PM +0100
On Thu, May 01, 2003 at 09:52:01PM +0100, Steven Whitehouse wrote:
> --- linux-2.5.68-bk10/fs/seq_file.c Sun Apr 20 03:27:58 2003
> +++ linux/fs/seq_file.c Mon Apr 21 14:40:35 2003
> @@ -338,3 +338,13 @@
> kfree(op);
> return res;
> }
> +
> +int kfree_release(struct inode *inode, struct file *file)
> +{
> + struct seq_file *seq = file->private_data;
> +
> + kfree(seq->private);
> + seq->private = NULL;
> + return seq_release(inode, file);
> +}
The name is a bit generic for an export function. What about
seq_release_kfree?
next prev parent reply other threads:[~2003-05-01 20:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030421.234303.59654654.davem@redhat.com>
2003-05-01 13:27 ` Remains of seq_file conversion for DECnet, plus fixes Steven Whitehouse
2003-05-01 12:45 ` David S. Miller
2003-05-01 14:04 ` Steven Whitehouse
2003-05-01 13:09 ` David S. Miller
2003-05-01 20:52 ` Steven Whitehouse
2003-05-01 20:57 ` Christoph Hellwig [this message]
2003-05-01 21:35 ` Steven Whitehouse
2003-05-01 21:22 ` David S. Miller
2003-05-02 1:54 ` Arnaldo Carvalho de Melo
2003-05-04 18:43 ` Steven Whitehouse
2003-05-06 6:46 ` David S. Miller
2003-05-01 20:55 ` Remains of seq_file conversion for DECnet, plus fixes (part 2) Steven Whitehouse
2003-05-01 20:57 ` Remains of seq_file conversion for DECnet, plus fixes (part 3) Steven Whitehouse
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=20030501215709.A28210@infradead.org \
--to=hch@infradead.org \
--cc=Steve@ChyGwyn.com \
--cc=davem@redhat.com \
--cc=linux-decnet-user@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).