public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] morse code panics for 2.5.62
Date: Wed, 19 Feb 2003 10:07:43 +0100	[thread overview]
Message-ID: <20030219090743.GK351@lug-owl.de> (raw)
In-Reply-To: <20030218224946.GB1048@louise.pinerecords.com>

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

On Tue, 2003-02-18 23:49:46 +0100, Tomas Szepe <szepe@pinerecords.com>
wrote in message <20030218224946.GB1048@louise.pinerecords.com>:
> > [jbglaw@lug-owl.de]
> > 
> > Then, you can have
> > const char morses[] = {
> > 	MORSE2('A', '.', '-'),
> > 	MORSE4('B', '-', '.', '.', '.'),
> > 	MORSE4('C', '-', '.', '-', '.'),
> > 	MORSE3('D', '-', '.', '.'),
> > 	MORSE1('E', '.'),
> > 	MORSE4('F', '.', '.', '-', '.')
> > 	...
> > };
> > 
> > That's going to take exactly the same memory in the compiled vmlinux
> > image, *and* it's really readable:-) Of course, gcc will optimize any
> > added "bloat" away...
> 
> Looks good to me, can you send an updated patch?

Okay, I'll first have to import your original patch:-) and have a real
look at it (how does it exactly store the data...). Then, I'll do an
undated patch. Please give me an hour ot two...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur
    fuer einen Freien Staat voll Freier Bürger" | im Internet!
   Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-02-19  8:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 13:50 [PATCH] morse code panics for 2.5.62 Tomas Szepe
2003-02-18 14:17 ` Jan-Benedict Glaw
2003-02-18 16:00   ` Andrew Rodland
2003-02-18 17:12     ` Jan-Benedict Glaw
2003-02-18 22:49       ` Tomas Szepe
2003-02-19  9:07         ` Jan-Benedict Glaw [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=20030219090743.GK351@lug-owl.de \
    --to=jbglaw@lug-owl.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