From: Alex Elder <elder@linaro.org>
To: Borislav Petkov <bp@suse.de>
Cc: akpm@linux-foundation.org, kay@vrfy.org, pmladek@suse.cz,
john.stultz@linaro.org, jack@suse.cz,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] printk: more log flag simplification
Date: Tue, 22 Jul 2014 10:55:43 -0500 [thread overview]
Message-ID: <53CE897F.4090308@linaro.org> (raw)
In-Reply-To: <20140722142456.GB10670@pd.tnic>
On 07/22/2014 09:24 AM, Borislav Petkov wrote:
> On Tue, Jul 22, 2014 at 09:01:55AM -0500, Alex Elder wrote:
>> This series eliminates the LOG_CONT entirely from the printk/log code.
>> It builds on another series, posted earlier today:
>> http://www.spinics.net/lists/kernel/msg1791665.html
>> This series was originally longer, but in review I was reminded
>> that some of the simplifications I had done were not valid.
>>
>> The first patch exploits the fact that LOG_CONT and LOG_NEWLINE
>> are inverses, and uses LOG_NEWLINE (or its negation) anywhere
>> LOG_CONT is used. As a result, LOG_CONT is no longer needed, so
>> it's eliminated.
>>
>> The second patch improves some comments and makes a few small
>> code cleanups, now that it's gone through this transformation.
>
> This is getting ridiculous - you've been spamming me with printk patches
> like crazy every day! I told you to wait a bit with a resend until
> people have had a chance to review them, but you don't seem to care.
>
> Would you please remove me from your CC list?
Yes. -Alex
> Thank you.
>
prev parent reply other threads:[~2014-07-22 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 14:01 [PATCH v2 0/2] printk: more log flag simplification Alex Elder
2014-07-22 14:01 ` [PATCH v2 1/2] printk: kill LOG_CONT Alex Elder
2014-07-22 14:01 ` [PATCH v2 2/2] printk: improve some commentary; tidy up Alex Elder
2014-07-22 14:24 ` [PATCH v2 0/2] printk: more log flag simplification Borislav Petkov
2014-07-22 15:55 ` Alex Elder [this message]
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=53CE897F.4090308@linaro.org \
--to=elder@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.cz \
/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.