From: Roland Dreier <roland@topspin.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devfs (2/7) - minor miscdev changes
Date: 18 Apr 2003 09:29:00 -0700 [thread overview]
Message-ID: <52znmn7os3.fsf@topspin.com> (raw)
In-Reply-To: <20030418181250.B363@lst.de>
int misc_register(struct miscdevice * misc)
{
- static devfs_handle_t devfs_handle, dir;
struct miscdevice *c;
+ char buf[256];
Wouldn't it be better not to have a 256-byte buffer on the stack?
- Roland
next prev parent reply other threads:[~2003-04-18 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 16:12 [PATCH] devfs (2/7) - minor miscdev changes Christoph Hellwig
2003-04-18 16:29 ` Roland Dreier [this message]
2003-04-18 17:03 ` Christoph Hellwig
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=52znmn7os3.fsf@topspin.com \
--to=roland@topspin.com \
--cc=hch@lst.de \
--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