From: dinguyen@altera.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCHv3 1/2] clocksource: dw_apb_timer: Move timer defines to header file.
Date: Tue, 17 Sep 2013 17:12:47 -0500 [thread overview]
Message-ID: <1379455967.14195.3.camel@linux-builds1> (raw)
In-Reply-To: <alpine.DEB.2.02.1309172337570.4089@ionos.tec.linutronix.de>
On Tue, 2013-09-17 at 23:45 +0200, Thomas Gleixner wrote:
> On Tue, 17 Sep 2013, Dinh Nguyen wrote:
>
> > On Wed, 2013-08-28 at 21:53 -0500, Dinh Nguyen wrote:
> > > From: Dinh Nguyen <dinguyen@altera.com>
> > >
> > > Move all dw_apb_timer defines to include/linux/dw_apb_timer.h.
>
> That's describing WHAT the patch does not WHY. I can see the WHAT part
> without that pointless changelog.
Will fix..
>
> >
> > Ping? This patch series has sat idle for 2-weeks now.
>
> So what?
>
> Sending non urgent (i.e. bug fixes, regression fixes etc.) patches at
> the beginning of the merge window begs for a 2 weeks delay. Well
> documented procedure...
Sorry, but it was just a friendly ping...didn't mean to imply any
urgency. The original patch was sent on 8/21, so patch has been around
for ~4 weeks..
Thanks for the review.
Dinh
>
>
> Thanks,
>
> tglx
>
prev parent reply other threads:[~2013-09-17 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 2:53 [RESEND PATCHv3 1/2] clocksource: dw_apb_timer: Move timer defines to header file dinguyen at altera.com
2013-08-29 2:53 ` [RESEND PATCHv3 2/2] clocksource: dw_apb_timer_of: Fix read_sched_clock dinguyen at altera.com
2013-09-17 16:14 ` [RESEND PATCHv3 1/2] clocksource: dw_apb_timer: Move timer defines to header file Dinh Nguyen
2013-09-17 21:45 ` Thomas Gleixner
2013-09-17 21:55 ` Pavel Machek
2013-09-17 22:14 ` Thomas Gleixner
2013-09-18 10:49 ` Pavel Machek
2013-09-17 22:12 ` Dinh Nguyen [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=1379455967.14195.3.camel@linux-builds1 \
--to=dinguyen@altera.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).