From: Paul Mundt <lethal@linux-sh.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: What's in sh-2.6.git for 2.6.25?
Date: Wed, 16 Jan 2008 09:37:18 +0000 [thread overview]
Message-ID: <20080116093718.GB14107@linux-sh.org> (raw)
In-Reply-To: <20080116073844.GA25205@uranus.ravnborg.org>
On Wed, Jan 16, 2008 at 08:38:44AM +0100, Sam Ravnborg wrote:
> On Wed, Jan 16, 2008 at 04:04:03PM +0900, Paul Mundt wrote:
> > This is a brief summary of the changes that are sitting in the sh queue
> > for 2.6.25.
> >
> > The main points to note are as follows:
> >
> > - sh64->sh integration.
> > - A handful of new CPUs (SH7721, SH7763, SH7203, SH7263).
> > - SH-2A FPU support.
> > - Board support updates (R2D, R7785RP).
> >
> > The sh64->sh integration is basically the only thing that's really
> > interesting, and so it's worth summarizing that a bit.
>
> Any kbuild bits that needs an extra pair of eyes before
> integration or can I postpone my review until it hits mainline?
> If you feel confident I prefer to wait as I'm busy atm.
>
Most of the kbuild bits have been pretty painless. I started out going
the SRCARCH route, but that ended up creating a lot of additional
duplication, so I opted to just roll them together and stick with abusing
KCONFIG_ALLCONFIG for restricting the options. Based on the heavy sharing
between the Kconfig options, this seemed to be the best way to go.
So, I'm reasonably content with it the way it is, but any input you have
on cleaning it up is certainly welcome at any time :-)
next prev parent reply other threads:[~2008-01-16 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 7:04 What's in sh-2.6.git for 2.6.25? Paul Mundt
2008-01-16 7:38 ` Sam Ravnborg
2008-01-16 9:37 ` Paul Mundt [this message]
2008-01-16 10:17 ` Sam Ravnborg
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=20080116093718.GB14107@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sam@ravnborg.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