From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Joe Perches <joe@perches.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Andreas Kemnade <andreas@kemnade.info>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: Fix __show_regs output timestamps
Date: Thu, 4 May 2017 09:27:50 +0100 [thread overview]
Message-ID: <3401f323-a4fa-a636-e032-d033ad059646@arm.com> (raw)
In-Reply-To: <1493857488.22125.31.camel@perches.com>
On 04/05/17 01:24, Joe Perches wrote:
> On Wed, 2017-05-03 at 22:30 +0100, Russell King - ARM Linux wrote:
>> On Wed, May 03, 2017 at 12:44:11PM -0700, Joe Perches wrote:
>>> On Wed, 2017-05-03 at 20:23 +0100, Russell King - ARM Linux wrote:
>>>> On Wed, Apr 26, 2017 at 10:39:49AM -0700, Joe Perches wrote:
>>>>> Multiple line formats are not preferred as the second and
>>>>> subsequent lines may not have timestamps.
>>>>>
>>>>> Lacking timestamps makes reading the output a bit difficult.
>>>>> This also makes arm/arm64 output more similar.
>>>>>
>>>>> Previous:
>>>>>
>>>>> [ 1514.093231] pc : [<bf79c304>] lr : [<bf79ced8>] psr: a00f0013
>>>>> sp : ecdd7e20 ip : 00000000 fp : ffffffff
>>>>>
>>>>> New:
>>>>>
>>>>> [ 1514.093231] pc : [<bf79c304>] lr : [<bf79ced8>] psr: a00f0013
>>>>> [ 1514.105316] sp : ecdd7e20 ip : 00000000 fp : ffffffff
>>>>>
>>>>> Signed-off-by: Joe Perches <joe@perches.com>
>>>>
>>>> Hi Joe,
>>>>
>>>> Could you put this in my patch system please, I'm unlikely to remember to
>>>> apply it otherwise if not already there (massive email backlog.)
>>>>
>>>> Thanks.
>>>
>>> Your patch system bounced my perfectly formatted patch
>>> because your system wants totally unnecessary additional
>>> information specific to your workflow.
>>>
>>> No thanks, I don't need the additional work just to
>>> please your system and neither should anyone else.
>>
>> Don't expect me to remember to apply your patch then. I've got days of
>> catch up, and I'm just not going to remember. Sorry.
>
> <shrug>
>
> If your systems require special handling on the
> part of patch submitters, you should document it
> in the kernel tree.
>
> Better, someone else should find the time to apply
> properly formatted patches.
>
Joe, I find this patch handy, so I've uploaded it into Russell's patch system
on your behalf and it has been accepted as patch 8673/1.
Cheers
Vladimir
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
prev parent reply other threads:[~2017-05-04 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 17:39 [PATCH] ARM: Fix __show_regs output timestamps Joe Perches
2017-04-26 20:18 ` Andreas Kemnade
2017-05-03 19:23 ` Russell King - ARM Linux
2017-05-03 19:40 ` Joe Perches
2017-05-03 19:44 ` Joe Perches
2017-05-03 21:30 ` Russell King - ARM Linux
2017-05-04 0:24 ` Joe Perches
2017-05-04 8:27 ` Vladimir Murzin [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=3401f323-a4fa-a636-e032-d033ad059646@arm.com \
--to=vladimir.murzin@arm.com \
--cc=andreas@kemnade.info \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox