netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Oeser <netdev@axxeo.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: netdev@vger.kernel.org, rt2x00-devel@lfcorreia.dyndns.org
Subject: Re: [PATCH 7/32] rt2x00: make vals static
Date: Fri, 28 Apr 2006 13:26:43 +0200	[thread overview]
Message-ID: <200604281326.43769.netdev@axxeo.de> (raw)
In-Reply-To: <200604280002.58147.IvDoorn@gmail.com>

Sie schrieben:
> From: Ivo van Doorn <IvDoorn@gmail.com>
> 
> The vals[] arrays in *_init_hw_channels can be made
> static to optimize memory and reduce stack size.

What about static const? They are also constants, right?
But please try first, if this helps in terms of code size.

Regards

Ingo Oeser

  reply	other threads:[~2006-04-28 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 22:02 [PATCH 7/32] rt2x00: make vals static Ivo van Doorn
2006-04-28 11:26 ` Ingo Oeser [this message]
2006-04-28 13:40   ` Ivo van Doorn

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=200604281326.43769.netdev@axxeo.de \
    --to=netdev@axxeo.de \
    --cc=ivdoorn@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rt2x00-devel@lfcorreia.dyndns.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).