Message-ID: <20071112154456.GH6347@axis.com>
Date:	Mon, 12 Nov 2007 16:44:56 +0100
From:	Jesper Nilsson <jesper.nilsson@...s.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	mikael.starvik@...s.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] CRISv10 improve and bugfix fasttimer

On Fri, Nov 09, 2007 at 03:19:32PM -0800, Andrew Morton wrote:
> On Thu, 8 Nov 2007 09:54:30 +0100
> Jesper Nilsson <jesper.nilsson@...s.com> wrote:
> 
> > Improve and bugfix CRIS v10 fast timers.
> 
> I'm trying to work out what's going on with all this cris activity.  Is the
> current code really that busted, or are you adding new chip support, or are
> you resyncing mainline with some external tree or what?

The answer is actually "all of the above". Axis has a CVS tree
that has gotten out of sync with mainline (although we've continued
to merge new releases regularly into our CVS).

This means that the CRISv10 architecture has gotten broken in mainline,
but we've done the corrections in our CVS.
My patches up to now has been focused on merging the ones that
makes the architecture compile.

There's the CRISv32 architecture for the Etrax FS chip (which I'm not
sure if it actually has worked at any time, since it is missing a
number of key drivers like ethernet and serial) which is a working
architecture here at Axis.

There's also a new chip Artpec-3 which is based on the CRISv32
architecture, and shares most (if not all) drivers with Etrax FS,
but has some different hardware configuration.

Lastly, there's a number of changes that are general bugfixes or
improvements but are not required to compile.

The ultimate goal is to get where our tree tracks mainline
as close as possible.

> It _seems_ that pretty much everything you've sent over is a bugfix of some
> form.  Should we push it all into 2.6.24?

Yes, that would be great.

> > -void __INLINE__ do_gettimeofday_fast(struct timeval *tv)
> > +void __INLINE__ do_gettimeofday_fast(struct fasttime_t *tv)
> 
> You might like to dispose of __INLINE__ sometime.  I doubt if there's
> really any need for it, and using plain old inline everywhere would be
> nicer.

Yes, it is certainly so when the file defines __INLINE__ to be inline.
I'll submit a later patch that removes this.

> >      /* Has it really expired? */
> 
> heh, so the old code used a bizarre random-number-of-spaces for indenting
> and the edits use tabs.

> Suggest that you consider a large-scale cleaup during some quiet time. 
> Often people will feed the file wholesale through scripts/Lindent and will
> then fix up Lindent mistakes by hand.  If you go this way, please do it as
> two separate patches.  That way if the huge cleanup patch breaks due to
> other changes I can rerun Lindent and the manual fix-Lindents-mistakes
> patch usually applies easily on top of the newly-generated
> run-it-through-Lindent patch.

Yup, I've actually used tabs on purpose to cut down on checkpatch
warnings, with just the intention of submitting the complete reformatting
as a separate patch later.

> >      if (timeval_cmp(&t->tv_expires, &tv) <= 0)
> 
> You have a private timeval_cmp().  Please take a look at utilising
> include/linux/time.h:timeval_compare() instead.  If that doesn't suit then
> we'd entertain extensions of that interface.  Adding private code to do
> something as common as this is not a good thing.

Ok, will do.

Thanks a lot for your time!

/^JN - Jesper Nilsson
--
               Jesper Nilsson -- jesper.nilsson@...s.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists