lkml.org 
[lkml]   [2020]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] ttyprintk: optimize tpk_close flush code
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Thu, Nov 12, 2020 at 09:41:22PM +0800, sunjunyong wrote:
> Hi Greg:
> It have no logic that handles NULL in tpk_flush() but tpk_printk().

Sorry, yes, that is what I mean.

> Do you mean that if i understand correctly?!I think we should not remove
> the logic that handles NULL in tpk_printk() as we don't know if the buf
> from parent caller is null or not.

Yes you do, you control that buffer right? This is a static function,
you know what is happening here.

> But we transfer a null buf to tpk_printk()
> for previous version of tpk_close, i think it's redundant.
>
> The comment is a hitory tip for other guys to understand.I suggest to
> keep it as before if you like.

The call to flush makes it obvious, no need to keep it. And we have git
history for people to look at if they are curious about past versions.

thanks,

greg k-h

\
 
 \ /
  Last update: 2020-11-12 18:17    [W:0.343 / U:0.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site