From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH printk v2 3/3] printk: remove dict ring
Date: Mon, 21 Sep 2020 11:56:33 +0200 [thread overview]
Message-ID: <20200921095633.GI14605@alley> (raw)
In-Reply-To: <20200918223421.21621-4-john.ogness@linutronix.de>
On Sat 2020-09-19 00:40:21, John Ogness wrote:
> Since there is no code that will ever store anything into the dict
> ring, remove it. If any future dictionary properties are to be
> added, these should be added to the struct printk_info.
>
> Signed-off-by: John Ogness <john.ogness@linutronix.de>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2020-09-21 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 22:34 [PATCH printk v2 0/3] printk: move dictionaries to meta data John Ogness
2020-09-18 22:34 ` [PATCH printk v2 1/3] printk: move printk_info into separate array John Ogness
2020-09-21 9:28 ` Petr Mladek
2020-09-18 22:34 ` [PATCH printk v2 2/3] printk: move dictionary keys to dev_printk_info John Ogness
2020-09-21 9:55 ` Petr Mladek
2020-09-21 11:12 ` [PATCH printk v3 " John Ogness
2020-09-21 11:18 ` [PATCH printk v4 " John Ogness
2020-09-21 13:56 ` Petr Mladek
2020-09-18 22:34 ` [PATCH printk v2 3/3] printk: remove dict ring John Ogness
2020-09-21 9:56 ` Petr Mladek [this message]
2020-09-22 10:02 ` [PATCH printk v2 0/3] printk: move dictionaries to meta data Petr Mladek
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=20200921095633.GI14605@alley \
--to=pmladek@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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