From: Tony Luck <tony.luck@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Kosina <jikos@kernel.org>,
Colin Ian King <colin.king@canonical.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] trivial for 4.9
Date: Fri, 7 Oct 2016 16:09:51 -0700 [thread overview]
Message-ID: <CA+8MBbJFD69qGiJQ1odu2ZczDoxbvViS+i6EbsLFX-zApBO4yQ@mail.gmail.com> (raw)
In-Reply-To: <CA+8MBb+xMS1Yr9dJG4gMmcp4x-XY4+UDGQ+=O7pZ51n8sYE8Ww@mail.gmail.com>
On Fri, Oct 7, 2016 at 4:01 PM, Tony Luck <tony.luck@gmail.com> wrote:
> What if there isn't a "next printk" call for hours, or days?
>
> That poor little message without a "\n" will sit in the kernel buffers,
> and the user who might want to see the message can't, until some
> unrelated thing happens to print something.
Retracted ... I'm sure that at some point in the past it happened like
that ... but
I just retested on 4.8 and the first message (with no "\n") showed up on the
serial port just fine without some other message to push it out. When the
next message came along, a "\n" was auto-inserted.
-Tony
next prev parent reply other threads:[~2016-10-07 23:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 8:51 [GIT PULL] trivial for 4.9 Jiri Kosina
2016-10-07 19:22 ` Linus Torvalds
2016-10-07 20:04 ` Joe Perches
2016-10-07 20:13 ` Linus Torvalds
2016-10-07 20:18 ` Joe Perches
2016-10-07 20:25 ` Linus Torvalds
2016-10-07 20:33 ` Joe Perches
2016-10-07 21:06 ` Linus Torvalds
2016-10-07 21:37 ` Linus Torvalds
2016-10-08 7:36 ` Joe Perches
2016-10-10 5:48 ` Joe Perches
2016-10-07 21:44 ` Joe Perches
2016-10-07 23:01 ` Tony Luck
2016-10-07 23:09 ` Tony Luck [this message]
2016-10-07 23:36 ` Linus Torvalds
2016-10-08 13:16 ` Steven Rostedt
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=CA+8MBbJFD69qGiJQ1odu2ZczDoxbvViS+i6EbsLFX-zApBO4yQ@mail.gmail.com \
--to=tony.luck@gmail.com \
--cc=colin.king@canonical.com \
--cc=jikos@kernel.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.