From: Joe Perches <joe@perches.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: linux-kernel@vger.kernel.org,
Andreas Kemnade <andreas@kemnade.info>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: Fix __show_regs output timestamps
Date: Wed, 03 May 2017 12:44:11 -0700 [thread overview]
Message-ID: <1493840651.22125.24.camel@perches.com> (raw)
In-Reply-To: <20170503192310.GD22219@n2100.armlinux.org.uk>
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.
next prev parent reply other threads:[~2017-05-03 19:44 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 [this message]
2017-05-03 21:30 ` Russell King - ARM Linux
2017-05-04 0:24 ` Joe Perches
2017-05-04 8:27 ` Vladimir Murzin
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=1493840651.22125.24.camel@perches.com \
--to=joe@perches.com \
--cc=andreas@kemnade.info \
--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