mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: akpm@linux-foundation.org, johnstul@us.ibm.com,
	ralf@linux-mips.org, anemo@mba.ocn.ne.jp,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clocksource: shift helper
Date: Tue, 6 May 2008 23:19:56 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805062303060.3318@apollo.tec.linutronix.de> (raw)
In-Reply-To: <1210107675.17132.181.camel@localhost.localdomain>

On Tue, 6 May 2008, Daniel Walker wrote:
> On Tue, 2008-05-06 at 22:53 +0200, Thomas Gleixner wrote:
> > 
> > And your description led me to the assumption that the code was pulled
> > from the MIPS git tree and not from the MIPS architecture code in
> > mainline. Everyone else I talked to was having the same impression.
> > 
> > I was wrong, but can you understand that your sloppy wording "pulled
> > from the MIPS tree" along with the fact that you just copied code
> > instead of moving it into the generic space and cleanup the MIPS code
> > where it is duplicated from is causing such a misunderstanding ?
> 
> You could have asked me if it was mainline or not. I can see how words
> could be misunderstood .

You - the patch submitter - have to provide useful information to
those who review the patches and not the reviewers are supposed to
decode your sloppy commit log.

"... which I pulled from the MIPS tree"

Why should I assume that this is from mainline ?

> > I'm fine with the change itself, but it needs to move the code out of
> > MIPS in the first place and not just duplicating code for no good
> > reason.
> 
> I can work with Atsushi, but I still think the generic version should be
> merged. We at least would need it in order to modify the mips code.

You can think what you want, it's not the way it works.

You duplicate code, so the first thing to do is to replace the code
which you copied and make sure it is still fully functional. Then you
can add a second user to make the point that the generic code move is
actually useful. btw, pmtimer is the worst example for a good use case
as everything there is constant so we can do it at compile time.

Thanks,
	tglx


  parent reply	other threads:[~2008-05-06 21:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 17:31 Daniel Walker
2008-05-01 19:32 ` Andrew Morton
2008-05-01 19:48   ` Daniel Walker
2008-05-01 21:05     ` Ralf Baechle
2008-05-06  0:52 ` Thomas Gleixner
2008-05-06 16:39   ` Daniel Walker
2008-05-06 20:25     ` Thomas Gleixner
2008-05-06 20:33       ` Daniel Walker
2008-05-06 20:53         ` Thomas Gleixner
2008-05-06 21:01           ` Daniel Walker
2008-05-06 21:18             ` Andrew Morton
2008-05-06 21:21               ` Thomas Gleixner
2008-05-06 21:19             ` Thomas Gleixner [this message]
2008-05-06 21:30               ` Daniel Walker
2008-05-07 16:23     ` Atsushi Nemoto
2008-05-07  3:57 ` Roman Zippel
2008-05-08 16:48   ` Daniel Walker

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=alpine.LFD.1.10.0805062303060.3318@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=dwalker@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.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

all inboxes | Powered by JetHome®