From: Jan Kara <jack@suse.cz>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
jslaby@suse.cz, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"kay.sievers" <kay.sievers@vrfy.org>
Subject: Re: [RFC][PATCH] printk: Remove separate printk_sched buffers and use printk buf instead
Date: Fri, 15 Feb 2013 18:00:18 +0100 [thread overview]
Message-ID: <20130215170018.GG7458@quack.suse.cz> (raw)
In-Reply-To: <1360947217.23152.112.camel@gandalf.local.home>
On Fri 15-02-13 11:53:37, Steven Rostedt wrote:
> 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.
Yeah, I understand. I use mutt and it automatically includes text/plain
attachments into reply for me so I barely notice a difference between
inline and attached patch. But with other clients it may be a hassle...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-02-15 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 1:05 [RFC][PATCH] printk: Remove separate printk_sched buffers and use printk buf instead Steven Rostedt
2013-02-06 14:32 ` Jan Kara
2013-02-06 23:02 ` Jan Kara
2013-02-12 12:22 ` Jan Kara
2013-02-14 18:48 ` Steven Rostedt
2013-02-15 16:50 ` Jan Kara
2013-02-15 16:53 ` Steven Rostedt
2013-02-15 17:00 ` Jan Kara [this message]
2013-02-15 16:54 ` Jan Kara
2013-02-15 16:57 ` [PATCH 3/3] printk: Avoid softlockups in console_unlock() Jan Kara
2013-02-15 22:22 ` Andrew Morton
2013-02-18 16:31 ` Jan Kara
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=20130215170018.GG7458@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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.