From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] [v2] hvc_dcc: don't ignore errors during initialization
Date: Wed, 19 Aug 2015 17:51:23 -0500 [thread overview]
Message-ID: <55D5086B.7050907@codeaurora.org> (raw)
In-Reply-To: <20150810094859.GF1604@arm.com>
On 08/10/2015 04:48 AM, Will Deacon wrote:
>> >
>> > static int __init hvc_dcc_console_init(void)
>> > {
>> >+ int ret;
>> >+
>> >+ /* This always runs on boot core */
> Does this really "always run on the boot core"? I couldn't find anything
> suggesting that console_init is limited in that regard.
So this is a left-over comment from some other code that actually cared
what code this function runs on. I've removed the comment.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2015-08-19 22:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 0:16 [PATCH 1/3] [v2] hvc_dcc: don't ignore errors during initialization Timur Tabi
2015-08-08 0:16 ` [PATCH 2/3] [v4] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc Timur Tabi
2015-08-10 9:40 ` Will Deacon
2015-08-17 23:56 ` Timur Tabi
2015-08-18 8:21 ` Dave Martin
2015-08-18 19:07 ` Timur Tabi
2015-08-19 10:14 ` Dave Martin
2015-08-19 16:16 ` Timur Tabi
2015-08-19 16:37 ` Dave Martin
2015-08-24 23:51 ` sboyd at codeaurora.org
2015-09-02 11:10 ` Dave Martin
2015-08-08 0:16 ` [PATCH 3/3] [v2] hvc_dcc: disable user-space access to DCC Timur Tabi
2015-08-10 9:47 ` Will Deacon
2015-08-17 22:45 ` Timur Tabi
2015-08-10 9:48 ` [PATCH 1/3] [v2] hvc_dcc: don't ignore errors during initialization Will Deacon
2015-08-19 22:51 ` Timur Tabi [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=55D5086B.7050907@codeaurora.org \
--to=timur@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.