public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <anton@enomsg.org>
To: Alexey Perevalov <a.perevalov@samsung.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, john.stultz@linaro.org,
	anton@nomsg.org, kyungmin.park@samsung.com,
	cw00.choi@samsung.com, akpm@linux-foundation.org
Subject: Re: [PATCH v3 4/6] timerfd: Factor out timer-type unspecific timerfd_expire()
Date: Thu, 20 Feb 2014 20:13:25 -0800	[thread overview]
Message-ID: <20140221041325.GA19817@teo> (raw)
In-Reply-To: <alpine.DEB.2.02.1402201136500.4468@ionos.tec.linutronix.de>

On Thu, Feb 20, 2014 at 11:52:03AM +0100, Thomas Gleixner wrote:
> > From: Anton Vorontsov <anton@enomsg.org>
> > 
> > There is nothing hrtimer-specific inside the timerfd_tmrproc(), except
> > the function prototype. We're about to add other timer types, so factor
> > out generic timerfd_expire() helper from timerfd_tmrproc().
> 
> This changelog is completely useless. How is timerfd_tmrproc, which is
> not a function but a function pointer, related to the patch?
> 
> Moving duplicated code to a common function is nice, but ....

> > Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
> > Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
... 
> Warnings are there to be ignored and testing of user space
> interfaces after a change is overrated, right?
> 
> Aside of that you just blindly copied the original code w/o fixing up
> the now unnecessary line breaks.

Alexey,

While I appreciate the desire to be careful with authorship and stuff,
please remove my name as an author of this patch -- the current code has
nothing to do with my original work, and I surely don't want to take any
responsibility for it. This is a common practice if you modify someone's
patch to a great extend.

Thomas is bashing the thing, which has my name on it; although _my_ patch
did not produce any warnings, came with a completely different changelog,
and served completely different purposes.

Instead of rushing with resending yet another series, please actually read
Thomas' review.

Thanks,

Anton

  parent reply	other threads:[~2014-02-21  4:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  8:40 [PATCH v3 0/6] Deferrable timers support for hrtimers/timerfd API Alexey Perevalov
2014-02-20  8:40 ` [PATCH v3 1/6] tracing/trivial: Add CLOCK_BOOTIME and CLOCK_TAI for human readable clockid trace Alexey Perevalov
2014-02-20 11:01   ` Thomas Gleixner
2014-02-20 16:25     ` Alexey Perevalov
2014-02-20  8:40 ` [PATCH v3 2/6] hrtimer: Add support for deferrable timer into the hrtimer Alexey Perevalov
2014-02-20 18:49   ` John Stultz
2014-02-20 21:18     ` Thomas Gleixner
2014-02-20 21:20       ` John Stultz
2014-02-20 21:56         ` Thomas Gleixner
2014-02-20  8:40 ` [PATCH v3 3/6] kernel/time: Add new helpers to convert ktime to/from jiffies Alexey Perevalov
2014-02-20 10:34   ` Thomas Gleixner
2014-02-20  8:40 ` [PATCH v3 4/6] timerfd: Factor out timer-type unspecific timerfd_expire() Alexey Perevalov
2014-02-20 10:52   ` Thomas Gleixner
2014-02-20 16:30     ` Alexey Perevalov
2014-02-21  4:13     ` Anton Vorontsov [this message]
2014-02-21  7:04       ` Alexey Perevalov
2014-02-21 10:41       ` Thomas Gleixner
2014-02-20  8:40 ` [PATCH v3 5/6] timerfd: Add support for deferrable timers Alexey Perevalov
2014-02-20 11:09   ` Thomas Gleixner
2014-02-21  4:11     ` Anton Vorontsov
2014-02-21 10:40       ` Thomas Gleixner
2014-02-20  8:40 ` [PATCH v3 6/6] tracing/trivial: Add CLOCK_*_DEFERRABLE for tracing clockids Alexey Perevalov
2014-02-20 11:12 ` [PATCH v3 0/6] Deferrable timers support for hrtimers/timerfd API Thomas Gleixner
2014-02-20 16:53   ` Alexey Perevalov
2014-02-20 21:21     ` Thomas Gleixner

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=20140221041325.GA19817@teo \
    --to=anton@enomsg.org \
    --cc=a.perevalov@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@nomsg.org \
    --cc=cw00.choi@samsung.com \
    --cc=john.stultz@linaro.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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