From: Aleksey Makarov <amakarov.linux@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Aleksey Makarov <aleksey.makarov@linaro.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Hurley <peter@hurleysoftware.com>,
Jiri Slaby <jslaby@suse.com>, Robin Murphy <robin.murphy@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
"Nair, Jayachandran" <Jayachandran.Nair@cavium.com>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH v3 3/3] printk: fix double printing with earlycon
Date: Tue, 7 Mar 2017 15:54:43 +0100 [thread overview]
Message-ID: <563502ae-1560-9dca-fe5b-4ec627c567f8@gmail.com> (raw)
In-Reply-To: <20170306145933.GB425@tigerII.localdomain>
On 03/06/2017 03:59 PM, Sergey Senozhatsky wrote:
> On (03/03/17 18:49), Aleksey Makarov wrote:
> [..]
>> +static enum { CONSOLE_MATCH, CONSOLE_MATCH_RETURN, CONSOLE_MATCH_NEXT }
>> +match_console(struct console *newcon, struct console_cmdline *c)
>
> that enum in function return is interesting :)
> can we make it less hackish?
We probably can, but I can not figure out how to do that.
Suggestions will be appreciated.
We should signal 3 different outcomes.
I thought that using standard errnos is not quite desciptive.
>> + if (!newcon->match ||
>> + newcon->match(newcon, c->name, c->index, c->options) != 0) {
>> + /* default matching */
>> + BUILD_BUG_ON(sizeof(c->name) != sizeof(newcon->name));
>> + if (strcmp(c->name, newcon->name) != 0)
>> + return CONSOLE_MATCH_NEXT;
>> + if (newcon->index >= 0 && newcon->index != c->index)
>> + return CONSOLE_MATCH_NEXT;
>
> who is checking CONSOLE_MATCH_NEXT?
The caller checks two other values, this one goes under the default case.
Should I check it explicitly?
>> + if (newcon->index < 0)
>> + newcon->index = c->index;
>> +
>> + if (_braille_register_console(newcon, c))
>> + return CONSOLE_MATCH_RETURN;
>> +
>> + if (newcon->setup &&
>> + newcon->setup(newcon, c->options) != 0)
>> + return CONSOLE_MATCH;
>> + }
>> +
>> + newcon->flags |= CON_ENABLED;
>> + return CONSOLE_MATCH;
>> +}
>> +
>> /*
>> * The console driver calls this routine during kernel initialization
>> * to register the console printing procedure with printk() and to
>> @@ -2454,40 +2480,50 @@ void register_console(struct console *newcon)
>> }
>>
>> /*
>> + * Check if this console was set as preferred by command line parameters
>> + * or by call to add_preferred_console(). There may be several entries
>> + * in the console_cmdline array matching with the same console so we
>> + * can not just use the first match. Instead check the entry pointed
>> + * by preferred_console and then all other entries.
>> + */
>> + if (preferred_console >= 0) {
>> + switch (match_console(newcon,
>> + console_cmdline + preferred_console)) {
>> + case CONSOLE_MATCH:
>> + if (newcon->flags | CON_ENABLED) {
>
> newcon->flags & CON_ENABLED ?
Sure. Thank you.
>> + newcon->flags |= CON_CONSDEV;
>> + has_preferred = true;
>> + }
>> + goto match;
>> + case CONSOLE_MATCH_RETURN:
>> + return;
>> + default:
>> + break;
>> + }
>> + }
>> +
>> + /*
>> * See if this console matches one we selected on
>> * the command line.
>> */
>> for (i = 0, c = console_cmdline;
>> i < MAX_CMDLINECONSOLES && c->name[0];
>> i++, c++) {
>> - if (!newcon->match ||
>> - newcon->match(newcon, c->name, c->index, c->options) != 0) {
>> - /* default matching */
>> - BUILD_BUG_ON(sizeof(c->name) != sizeof(newcon->name));
>> - if (strcmp(c->name, newcon->name) != 0)
>> - continue;
>> - if (newcon->index >= 0 &&
>> - newcon->index != c->index)
>> - continue;
>> - if (newcon->index < 0)
>> - newcon->index = c->index;
>> -
>> - if (_braille_register_console(newcon, c))
>> - return;
>>
>> - if (newcon->setup &&
>> - newcon->setup(newcon, c->options) != 0)
>> - break;
>> - }
>> + if (preferred_console == i)
>> + continue;
>>
>> - newcon->flags |= CON_ENABLED;
>> - if (i == preferred_console) {
>> - newcon->flags |= CON_CONSDEV;
>> - has_preferred = true;
>> + switch (match_console(newcon, c)) {
>> + case CONSOLE_MATCH:
>> + goto match;
>> + case CONSOLE_MATCH_RETURN:
>> + return;
>> + default:
>> + break;
>
> sorry, it was a rather long for me today. need to look more at this.
> for what is now CONSOLE_MATCH_NEXT we used to have continue,
CONSOLE_MATCH is for the case when the console matches against the description,
CONSOLE_MATCH_NEXT - it does not, we should try next,
CONSOLE_MATCH_RETURN - we should return as the braille console is registered now.
> and now we break out of the loop?
`goto match` or just when we have seen all the entries
Thank you
Aleksey Makarov
>
> -ss
> --
> To unsubscribe from this list: send the line "unsubscribe linux-serial" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-03-07 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 13:11 [PATCH v2 0/3] " Aleksey Makarov
2017-03-02 13:11 ` [PATCH v2 1/3] printk: fix name/type/scope of preferred_console var Aleksey Makarov
2017-03-02 14:49 ` Steven Rostedt
2017-03-02 15:59 ` Sergey Senozhatsky
2017-03-14 16:52 ` Petr Mladek
2017-03-02 13:11 ` [PATCH v2 2/3] printk: rename selected_console -> preferred_console Aleksey Makarov
2017-03-02 15:01 ` Steven Rostedt
2017-03-02 16:09 ` Sergey Senozhatsky
2017-03-15 9:00 ` Petr Mladek
2017-03-02 13:11 ` [PATCH v2 3/3] printk: fix double printing with earlycon Aleksey Makarov
2017-03-02 13:58 ` Aleksey Makarov
2017-03-03 15:49 ` [PATCH v3 " Aleksey Makarov
2017-03-06 14:59 ` Sergey Senozhatsky
2017-03-07 14:54 ` Aleksey Makarov [this message]
2017-03-08 5:33 ` Sergey Senozhatsky
2017-03-08 12:59 ` Aleksey Makarov
2017-03-14 16:17 ` [PATCH v2 0/3] " Sudeep Holla
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=563502ae-1560-9dca-fe5b-4ec627c567f8@gmail.com \
--to=amakarov.linux@gmail.com \
--cc=Jayachandran.Nair@cavium.com \
--cc=aleksey.makarov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=pmladek@suse.com \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=sudeep.holla@arm.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
all inboxes | Powered by JetHome®