From: Joe Perches <joe@perches.com>
To: Kay Sievers <kay@vrfy.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] printk(): add KERN_CONT where needed
Date: Tue, 03 Apr 2012 09:16:40 -0700 [thread overview]
Message-ID: <1333469800.26079.35.camel@joe2Laptop> (raw)
In-Reply-To: <CAPXgP11MBdqc3BiDLA1q5gW4BZy2q4PoLtD20oRXfKY+C-HOgw@mail.gmail.com>
On Tue, 2012-04-03 at 18:11 +0200, Kay Sievers wrote:
> On Tue, Apr 3, 2012 at 18:05, Joe Perches <joe@perches.com> wrote:
> > On Tue, 2012-04-03 at 17:50 +0200, Kay Sievers wrote:
> >> I did not claim to address the problem of concurrent continuation line
> >> writers, and this patch has absolutely nothing to do with that
> >> problem. It _does_ fix encountered problems,
> >
> > No it doesn't. It fixes problems _you_ encounter
> > with an unpublished modification of the printk
> > subsystem.
>
> Exactly. And that is what is written in the changelog of the patch.
> But all that does not matter, the change results in more correct code
> than the current one is; and that is all that matters.
>
> Sure, I see your point, and support your effort, but I don't think
> your arguments are related to this patch and you are hijacking
> something unrelated, which should be discussed in a separate mail
> thread, that's all.
Conversations happen all over the place and making
separate discussions isn't that valuable nor are
they really controllable.
Just write the change log to simply state "add KERN_CONT"
without mentioning your unpublished stuff.
cheers, Joe
next prev parent reply other threads:[~2012-04-03 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 1:18 [PATCH] printk(): add KERN_CONT where needed Kay Sievers
2012-04-03 2:36 ` Joe Perches
2012-04-03 3:00 ` Kay Sievers
2012-04-03 3:03 ` Joe Perches
2012-04-03 3:47 ` Joe Perches
2012-04-03 10:30 ` Kay Sievers
2012-04-03 14:32 ` Joe Perches
2012-04-03 15:50 ` Kay Sievers
2012-04-03 16:05 ` Joe Perches
2012-04-03 16:11 ` Kay Sievers
2012-04-03 16:16 ` Joe Perches [this message]
2012-04-03 16:20 ` Kay Sievers
2012-04-03 16:27 ` Joe Perches
2012-04-09 23:08 ` Andrew Morton
2012-04-09 23:37 ` Joe Perches
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=1333469800.26079.35.camel@joe2Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kay@vrfy.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.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.