public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	x86 maintainers <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip] x86: cleanup 20090317
Date: Tue, 17 Mar 2009 11:26:29 +0100	[thread overview]
Message-ID: <20090317102629.GH6477@elte.hu> (raw)
In-Reply-To: <1237279833.3464.4.camel@ht.satnam>


* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:

> On Tue, 2009-03-17 at 09:38 +0100, Thomas Gleixner wrote:
> > On Tue, 17 Mar 2009, Jaswinder Singh Rajput wrote:
> > > On Mon, 2009-03-16 at 23:33 +0100, Thomas Gleixner wrote:
> > > > On Tue, 17 Mar 2009, Jaswinder Singh Rajput wrote:
> > > > 
> > > > > -static struct clock_event_device pit_clockevent = {
> > > > > +static struct clock_event_device pit_dev = {
> > > > 
> > > >   Why do we need to change the name of the variable ? Just for fun or
> > > >   is pit_dev more self explaining than pit_clockevent ?
> > > 
> > > pit already means it is a clock event, but with this change:
> > > 
> > > 1. we save 8 characters per declaration
> > > 2. It solves various 80 characters problem
> > 
> > There is not a single 80 character problem in that file.
> 
> Here are 80 character problems:
> 
> 1.        pit_clockevent.mult = div_sc(CLOCK_TICK_RATE, NSEC_PER_SEC,
>                                      pit_clockevent.shift);
> 2.        pit_clockevent.max_delta_ns =
>                 clockevent_delta2ns(0x7FFF, &pit_clockevent);
> 3.        pit_clockevent.min_delta_ns =
>                 clockevent_delta2ns(0xF, &pit_clockevent);
> 
> 4.        clocksource_pit.mult = clocksource_hz2mult(CLOCK_TICK_RATE,
>                                                    clocksource_pit.shift);

We could rename "pit_clockevent" to "pit_ce" perhaps - if Thomas 
agrees. pit_dev sounds weird.

pure (non-code-changing) cleanups should be kept separate from 
code changing cleanups.


	Ingo

      reply	other threads:[~2009-03-17 10:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 18:45 [git-pull -tip] x86: cleanup 20090317 Jaswinder Singh Rajput
2009-03-16 22:33 ` Thomas Gleixner
2009-03-17  5:26   ` Jaswinder Singh Rajput
2009-03-17  8:38     ` Thomas Gleixner
2009-03-17  8:50       ` Jaswinder Singh Rajput
2009-03-17 10:26         ` Ingo Molnar [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=20090317102629.GH6477@elte.hu \
    --to=mingo@elte.hu \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox