LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org> To: Andrew Morton <akpm@linux-foundation.org> Cc: linux-kernel@vger.kernel.org, Dmitry Torokhov <dtor@mail.ru>, Jiri Kosina <jkosina@suse.cz> Subject: Re: [PATCH2] Basic braille screen reader support Date: Sat, 23 Feb 2008 14:10:28 +0100 [thread overview] Message-ID: <20080223131028.GC4244@implementation> (raw) In-Reply-To: <20080223000410.674ce674.akpm@linux-foundation.org> Andrew Morton, le Sat 23 Feb 2008 00:04:10 -0800, a écrit : > > +++ linux-2.6.24.1-perso/kernel/printk.c 2008-02-21 12:09:06.000000000 +0100 > > @@ -105,6 +105,7 @@ > > Please use `diff -p' Argl, that's editdiff's fault. We need to fix it to keep the -p comments. > > char name[8]; /* Name of the driver */ > > int index; /* Minor dev. to use */ > > char *options; /* Options for the driver */ > > + char *brl_options; /* Options for braille driver */ > > }; > > Should this depend on CONFIG_A11Y_BRAILLE_CONSOLE or whatever? It can, indeed. It just makes the code a little more clumsy to save 32 or 64 bytes. > > + for (i = 0; i < MAX_CMDLINECONSOLES && console_cmdline[i].name[0]; i++) > > + if (strcmp(console_cmdline[i].name, name) == 0 && > > + console_cmdline[i].index == idx) { > > + if (!brl_options) > > + selected_console = i; > > + return 0; > > + } > > + if (i == MAX_CMDLINECONSOLES) > > + return -E2BIG; > > Does the array of consles have any locking here? Well, that's actually just the original code that I moved a bit earlier, so the code path is not changed. > > + if (!brl_options) > > + selected_console = i; > > + c = &console_cmdline[i]; > > + memcpy(c->name, name, sizeof(c->name)); > > + c->name[sizeof(c->name) - 1] = 0; > > strlcpy()? Again, that's the original code, unmodified, but we can put an strlcpy here yes. > > +static void beep(unsigned int freq) > > +{ > > + if (sound) > > + kd_mksound(freq, HZ/10); > > +} > > hm, do we have enough Kconfig dependencies here to ensure that kd_mksound() > is always available? Ah, CONFIG_VT is needed indeed. I'll address those in replies to this mail. Samuel
next prev parent reply other threads:[~2008-02-23 13:19 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-04 3:18 [PATCH] Basic braille screen reader support Samuel Thibault 2008-02-04 3:22 ` Samuel Thibault 2008-02-04 17:10 ` Greg KH 2008-02-04 17:24 ` Samuel Thibault 2008-02-04 18:06 ` Greg KH 2008-02-04 18:15 ` Samuel Thibault 2008-02-04 18:27 ` Greg KH 2008-02-05 22:00 ` [PATCH,RESEND] " Samuel Thibault 2008-02-06 0:58 ` Andrew Morton 2008-02-06 2:04 ` Samuel Thibault 2008-02-22 0:28 ` [PATCH2] " Samuel Thibault 2008-02-23 8:04 ` Andrew Morton 2008-02-23 13:10 ` Samuel Thibault [this message] 2008-02-23 13:15 ` [PATCH] Braille screen reader fixes Samuel Thibault 2008-02-23 13:17 ` [PATCH] Braille screen reader documentation Samuel Thibault 2008-04-24 0:39 ` [PATCH2] Basic braille screen reader support Samuel Thibault 2008-04-24 4:46 ` Andrew Morton 2008-04-24 10:21 ` Alan Cox 2008-04-24 11:09 ` Samuel Thibault 2008-03-19 18:57 ` [mmotm build error] Re: [PATCH,RESEND] " Randy Dunlap 2008-03-20 2:07 ` Samuel Thibault 2008-03-20 4:19 ` Randy Dunlap
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=20080223131028.GC4244@implementation \ --to=samuel.thibault@ens-lyon.org \ --cc=akpm@linux-foundation.org \ --cc=dtor@mail.ru \ --cc=jkosina@suse.cz \ --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: linkBe 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).