From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Jan Kara <jack@suse.com>, Petr Mladek <pmladek@suse.com>,
Tejun Heo <tj@kernel.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-kernel@vger.kernel.org,
Byungchul Park <byungchul.park@lge.com>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v10 1/2] printk: Make printk() completely async
Date: Tue, 5 Apr 2016 16:39:32 +0900 [thread overview]
Message-ID: <20160405073932.GA513@swordfish> (raw)
In-Reply-To: <20160405051717.GB1954@swordfish>
On (04/05/16 14:17), Sergey Senozhatsky wrote:
[..]
> > Could do with a comment explaining why late_initcall was chosen.
>
> late_initcall was chosen because of workqueue early_initcall, and
> I just decided not to change it when I switched from wq to a
> dedicated printk kthread. late_initcall seemed to be OK. can do
> init_printk_kthread() somewhere in init/main start_kernel().
or rather move it a bit earlier. core_init sounds appropriate;
or postcore. don't want to export yet another printk symbol.
-ss
next prev parent reply other threads:[~2016-04-05 7:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 16:57 [PATCH v10 0/2] printk: Make printk() completely async Sergey Senozhatsky
2016-04-04 16:57 ` [PATCH v10 1/2] " Sergey Senozhatsky
2016-04-04 22:51 ` Andrew Morton
2016-04-05 5:17 ` Sergey Senozhatsky
2016-04-05 7:39 ` Sergey Senozhatsky [this message]
2016-04-06 0:19 ` Sergey Senozhatsky
2016-04-06 8:27 ` Jan Kara
2016-04-07 9:48 ` Sergey Senozhatsky
2016-04-07 12:08 ` Sergey Senozhatsky
2016-04-07 13:15 ` Jan Kara
2016-08-10 21:17 ` Viresh Kumar
2016-08-12 9:44 ` Petr Mladek
2016-08-15 14:26 ` Vladislav Levenetz
2016-08-16 9:04 ` Petr Mladek
2016-08-18 2:27 ` Sergey Senozhatsky
2016-08-18 9:33 ` Petr Mladek
2016-08-18 9:51 ` Sergey Senozhatsky
2016-08-18 10:56 ` Petr Mladek
2016-08-19 6:32 ` Sergey Senozhatsky
2016-08-19 9:54 ` Petr Mladek
2016-08-19 19:00 ` Jan Kara
2016-08-20 5:24 ` Sergey Senozhatsky
2016-08-22 4:15 ` Sergey Senozhatsky
2016-08-23 12:19 ` Petr Mladek
2016-08-24 1:33 ` Sergey Senozhatsky
2016-08-25 21:10 ` Petr Mladek
2016-08-26 1:56 ` Sergey Senozhatsky
2016-08-26 8:20 ` Sergey Senozhatsky
2016-08-30 9:29 ` Petr Mladek
2016-08-31 2:31 ` Sergey Senozhatsky
2016-08-31 9:38 ` Petr Mladek
2016-08-31 12:52 ` Sergey Senozhatsky
2016-09-01 8:58 ` Petr Mladek
2016-09-02 7:58 ` Sergey Senozhatsky
2016-09-02 15:15 ` Petr Mladek
2016-09-06 7:16 ` Sergey Senozhatsky
2016-08-23 13:03 ` Petr Mladek
2016-08-23 13:48 ` Petr Mladek
2016-04-04 16:57 ` [PATCH v10 2/2] printk: Make wake_up_klogd_work_func() async Sergey Senozhatsky
2016-08-23 3:32 [PATCH v10 1/2] printk: Make printk() completely async Andreas Mohr
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=20160405073932.GA513@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=byungchul.park@lge.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).