From: Maninder Singh <maninder1.s@samsung.com>
To: pmladek@suse.com, sergey.senozhatsky@gmail.com, rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, a.sahrawat@samsung.com,
pankaj.m@samsung.com, v.narang@samsung.com,
Maninder Singh <maninder1.s@samsung.com>
Subject: [PATCH 1/2] printk: remove unused flag LOG_NOCONS
Date: Thu, 31 May 2018 15:47:51 +0530 [thread overview]
Message-ID: <20180531102133epcas5p2e8d47887c1708836c9b70964983093e2~zs4eTmEuv0380103801epcas5p2U@epcas5p2.samsung.com> (raw)
In-Reply-To: CGME20180531102133epcas5p2e8d47887c1708836c9b70964983093e2@epcas5p2.samsung.com
This patch removes unused flag LOG_NOCONS for printk.
usage of this flag is removed long back with below commit.
"5c2992ee7fd8a29d04125dc0aa3522784c5fa5eb"
printk: remove console flushing special cases for
partial buffered lines
Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
Signed-off-by: Vaneet Narang <v.narang@samsung.com>
---
kernel/printk/printk.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 2f4af21..ab15903 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -349,10 +349,9 @@ enum con_msg_format_flags {
*/
enum log_flags {
- LOG_NOCONS = 1, /* already flushed, do not print to console */
- LOG_NEWLINE = 2, /* text ended with a newline */
- LOG_PREFIX = 4, /* text started with a prefix */
- LOG_CONT = 8, /* text is a fragment of a continuation line */
+ LOG_NEWLINE = 1, /* text ended with a newline */
+ LOG_PREFIX = 2, /* text started with a prefix */
+ LOG_CONT = 4, /* text is a fragment of a continuation line */
};
struct printk_log {
--
1.9.1
next parent reply other threads:[~2018-05-31 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180531102133epcas5p2e8d47887c1708836c9b70964983093e2@epcas5p2.samsung.com>
2018-05-31 10:17 ` Maninder Singh [this message]
2018-05-31 10:54 ` [PATCH 1/2] printk: remove unused flag LOG_NOCONS Sergey Senozhatsky
2018-05-31 12:16 ` Petr Mladek
2018-05-31 15:12 ` Joe Perches
2018-06-05 12:59 ` Petr Mladek
2018-06-04 21:33 ` Steven Rostedt
2018-06-05 12:56 ` 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='20180531102133epcas5p2e8d47887c1708836c9b70964983093e2~zs4eTmEuv0380103801epcas5p2U@epcas5p2.samsung.com' \
--to=maninder1.s@samsung.com \
--cc=a.sahrawat@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.m@samsung.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=v.narang@samsung.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;
as well as URLs for NNTP newsgroup(s).