From: Greg KH <gregkh@linuxfoundation.org>
To: Preeti U Murthy <preeti@linux.vnet.ibm.com>
Cc: stable@vger.kernel.org, mingo@kernel.org, linux@roeck-us.net
Subject: Re: [PATCH3/5] tick: Simplify tick-internal.h
Date: Mon, 29 Jun 2015 15:49:22 -0700 [thread overview]
Message-ID: <20150629224922.GA19806@kroah.com> (raw)
In-Reply-To: <20150513115022.27807.79082.stgit@preeti.in.ibm.com>
On Wed, May 13, 2015 at 05:20:23PM +0530, Preeti U Murthy wrote:
> From: Thomas Gleixner <tglx@linutronix.de>
>
> commit b7475eb599ddb2e8cab2dc86ff38a9507463ad6b upstream
>
> tick-internal.h is pretty confusing as a lot of the stub inlines
> are there several times.
>
> Distangle the maze and make clear functional sections.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> [ rjw: Subject ]
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Link: http://lkml.kernel.org/r/16068264.vcNp79HLaT@vostro.rjw.lan
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Preeti U Murthy <preeti@linux.vnet.ibm.com>
You don't mention that you changed this function from what it is
upstream, which isn't ok to do without a good reason.
I'm really not liking this series, it's very intrusive for almost no
gain. In other words, you have a very specific platform, with limited
users, and a limited use case, yet are asking for core timer functions
to be made for a kernel that I'm going to stop maintaining after the
next release.
In other words, these patches are going to only have a lifespan of 1
more week, max. By then, all your users should be on 4.1, so 4.0
doesn't matter anymore.
So I'm just going to drop this whole series, sorry. If you have a
distro that "has to have these", then please work with them, otherwise,
just use 4.1, as all is good, and most importantly, properly tested,
there.
thanks,
greg k-h
next prev parent reply other threads:[~2015-06-29 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 11:49 [PATCH 0/5] Fix race in hrtimer broadcast and take care of dependencies Preeti U Murthy
2015-05-13 11:50 ` [PATCH1/5] clockevents: Remove CONFIG_GENERIC_CLOCKEVENTS_BUILD Preeti U Murthy
2015-05-13 11:50 ` [PATCH2/5] tick: Move clocksource related stuff to timekeeping.h Preeti U Murthy
2015-05-13 11:50 ` [PATCH3/5] tick: Simplify tick-internal.h Preeti U Murthy
2015-06-29 22:49 ` Greg KH [this message]
2015-06-30 3:24 ` Preeti U Murthy
2015-05-13 11:50 ` [PATCH4/5] tick: Move core only declarations and functions to core Preeti U Murthy
2015-05-13 11:50 ` [PATCH5/5] clockevents: Fix cpu_down() race for hrtimer based broadcasting Preeti U Murthy
2015-06-18 8:06 ` [PATCH 0/5] Fix race in hrtimer broadcast and take care of dependencies Preeti U Murthy
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=20150629224922.GA19806@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=mingo@kernel.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=stable@vger.kernel.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 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.