From: Jiri Benc <jbenc@suse.cz>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
Michael Wu <flamingice@sourmilk.net>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] conserve stack space due to padding
Date: Fri, 15 Jun 2007 15:30:53 +0200 [thread overview]
Message-ID: <20070615153053.37aaffb0@griffin.suse.cz> (raw)
In-Reply-To: <1181805971.9058.14.camel@johannes.berg>
On Thu, 14 Jun 2007 09:26:11 +0200, Johannes Berg wrote:
> This patch reorders some fields in struct ieee802_11_elems to save 17*7
> or 17*3 bytes (on 64/32-bit machines respectively) stack space in a few
> functions.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Acked-by: Jiri Benc <jbenc@suse.cz>
--
Jiri Benc
SUSE Labs
prev parent reply other threads:[~2007-06-15 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 7:26 [PATCH] conserve stack space due to padding Johannes Berg
2007-06-15 13:30 ` Jiri Benc [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=20070615153053.37aaffb0@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).