linux-kernel - Re: [RFC][PATCH] printk: Remove separate printk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1360947217.23152.112.camel@gandalf.local.home>
Date:	Fri, 15 Feb 2013 11:53:37 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jan Kara <jack@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>, jslaby@...e.cz,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"kay.sievers" <kay.sievers@...y.org>
Subject: Re: [RFC][PATCH] printk: Remove separate printk_sched buffers and
 use printk buf instead

On Fri, 2013-02-15 at 17:50 +0100, Jan Kara wrote:
> On Thu 14-02-13 13:48:11, Steven Rostedt wrote:
> > On Tue, 2013-02-12 at 13:22 +0100, Jan Kara wrote:
> > 
> > > > Anyway, what do you guys think about this version?
> > >   Steven, Andrew, did you have a chance to look at my patches?
> > 
> > Can you resend without being attachments. Patches sent as attachments
> > seldom get reviewed.
>   Well, for example I do review text/plain attachments but that may count
> into 'seldom' ;) I'll send them inline.
> 

The problem is that it makes it difficult to reply with comments. I
haven't looked at the patches yet so I may not have comments, but on my
email client, commenting attachments means that I need to cut and paste
the text to do the comment, which isn't the case for inline patches.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/