From: Ian Molton <ian.molton@collabora.co.uk>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Buffer allocation question
Date: Tue, 14 Sep 2010 18:43:00 +0100 [thread overview]
Message-ID: <4C8FB424.8010508@collabora.co.uk> (raw)
In-Reply-To: <4C8F1BC8.4010201@ladisch.de>
On 14/09/10 07:52, Clemens Ladisch wrote:
<>
Thanks!
I've decided to go for a fixed-buffer scheme in the end.
-Ian
prev parent reply other threads:[~2010-09-14 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 15:51 Buffer allocation question Ian Molton
2010-09-14 6:52 ` Clemens Ladisch
2010-09-14 17:43 ` Ian Molton [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=4C8FB424.8010508@collabora.co.uk \
--to=ian.molton@collabora.co.uk \
--cc=clemens@ladisch.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