From: Frank Seidel <fseidel@suse.de>
To: Frank Seidel <frank@f-seidel.de>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
akpm@linux-foundation.org, hannes@hanneseder.net,
johannes@sipsolutions.net,
"David S. Miller" <davem@davemloft.net>,
wangchen@cn.fujitsu.com,
"John W. Linville" <linville@tuxdriver.com>,
Frank Seidel <fseidel@suse.de>
Subject: Re: [PATCH][trivial] airo: reduce stack memory footpring
Date: Wed, 25 Feb 2009 15:44:54 +0100 [thread overview]
Message-ID: <49A55966.6000702@suse.de> (raw)
In-Reply-To: <49A5583D.5050502@f-seidel.de>
Sorry, $SUBJECT should of course be:
[PATCH][trivial] airo: reduce stack memory footprint
prev parent reply other threads:[~2009-02-25 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 14:39 [PATCH][trivial] airo: reduce stack memory footpring Frank Seidel
2009-02-25 14:44 ` Frank Seidel [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=49A55966.6000702@suse.de \
--to=fseidel@suse.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=frank@f-seidel.de \
--cc=hannes@hanneseder.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=wangchen@cn.fujitsu.com \
/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