From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Changki Kim <changki.kim@samsung.com>,
sergey.senozhatsky@gmail.com, rostedt@goodmis.org,
changbin.du@intel.com, masahiroy@kernel.org, rd.dunlap@gmail.com,
gregkh@linuxfoundation.org, krzk@kernel.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [POC] printk: Convert dict ring into array
Date: Fri, 11 Sep 2020 13:15:33 +0206 [thread overview]
Message-ID: <878sdgefiq.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20200911103217.GJ3864@alley>
On 2020-09-11, Petr Mladek <pmladek@suse.com> wrote:
> I would like to go this way in the long term because it looks like the
> most easy and reliable solution.
This change is technically trivial and I don't have any problems with
it. Actually it follows the agreement made at the meeting in Lisbon [0]
of "support for printk dictionaries will be discontinued".
So there will be no more dictionaries, but subsystem and device
information will continue to exist as extended record data.
John Ogness
[0] https://lkml.kernel.org/r/87k1acz5rx.fsf@linutronix.de
prev parent reply other threads:[~2020-09-11 11:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200904082449epcas2p4420d5df2083325b328a182c79f5c0948@epcas2p4.samsung.com>
2020-09-04 8:24 ` printk: Add process name information to printk() output Changki Kim
2020-09-04 9:05 ` Greg KH
2020-09-04 9:31 ` 김창기
2020-09-04 10:34 ` 'Greg KH'
2020-09-07 1:48 ` 김창기
2020-09-04 9:47 ` John Ogness
2020-09-04 10:35 ` Greg KH
2020-09-04 19:27 ` Joe Perches
2020-09-04 12:45 ` Petr Mladek
2020-09-04 13:17 ` John Ogness
2020-09-04 15:13 ` Petr Mladek
2020-09-04 23:27 ` John Ogness
2020-09-07 9:28 ` 김창기
2020-09-07 9:54 ` Petr Mladek
2020-09-07 10:30 ` John Ogness
2020-09-07 15:47 ` Petr Mladek
2020-09-11 9:50 ` [POC] printk: Convert dict ring into array Petr Mladek
2020-09-11 10:32 ` Petr Mladek
2020-09-11 11:09 ` John Ogness [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=878sdgefiq.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=changbin.du@intel.com \
--cc=changki.kim@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=pmladek@suse.com \
--cc=rd.dunlap@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
/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