public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@bitwizard.nl (Rogier Wolff)
To: Tigran Aivazian <tigran@veritas.com>
Cc: Patrick van de Lageweg <patrick@bitwizard.nl>,
	Rogier Wolff <wolff@bitwizard.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] New user space serial port driver
Date: Thu, 30 Nov 2000 10:47:34 +0100 (MET)	[thread overview]
Message-ID: <200011300947.KAA27728@cave.bitwizard.nl> (raw)
In-Reply-To: <Pine.LNX.4.21.0011300817320.846-100000@penguin.homenet> from Tigran Aivazian at "Nov 30, 2000 08:22:13 am"

Tigran Aivazian wrote:
> On Thu, 30 Nov 2000, Patrick van de Lageweg wrote:
> > +static struct tty_struct * ussp_table[USSP_MAX_PORTS] = { NULL, };
> 
> this wastes at least 4 * USSP_MAX_PORTS bytes in the kernel image.
> Typically around 64 bytes but could be more. For more info see the recent
> silly flamewars on the list.

And I think the guys who were saying that the "documentation is more
important than those few bytes" were winning. 

I am one of those guys. I think the documentation aspect is much more
important than those 64 bytes.

> The correct way is not to initialize the data
> to zero explicitly as BSS is cleared automatically on boot. It is also
> probably documented in the lkml FAQ at the bottom of this message.
> 
> Also, it makes your code look consistent as, e.g. in cases below you do
> the right thing:
> 
> > +static struct termios    * ussp_termios[USSP_MAX_PORTS];
> > +static struct termios    * ussp_termios_locked[USSP_MAX_PORTS];

this SHOULD mean that these are first initialized before use. 

If you think they can be used before first being initialized by the
code, then that's a bug, and I'll look into it.

			Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-30 10:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30  8:04 [PATCH] New user space serial port driver Patrick van de Lageweg
2000-11-30  8:22 ` Tigran Aivazian
2000-11-30  9:47   ` Rogier Wolff [this message]
2000-11-30 15:00     ` Russell King
2000-11-30 16:47       ` Rogier Wolff
2000-11-30 16:54         ` Russell King
2000-11-30 23:09           ` Rogier Wolff
2000-12-02 21:59 ` Pavel Machek
2000-12-07 12:38   ` Jamie Lokier

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=200011300947.KAA27728@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrick@bitwizard.nl \
    --cc=tigran@veritas.com \
    --cc=wolff@bitwizard.nl \
    /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