From: Sam Ravnborg <sam@ravnborg.org>
To: David Howells <dhowells@redhat.com>,
Koichi Yasutake <yasutake.koichi@jp.panasonic.com>,
linux-am33-list@redhat.com
Cc: linux arch <linux-arch@vger.kernel.org>
Subject: mn10300: Any plans to introduce arch/mn10300/include?
Date: Tue, 25 Nov 2008 21:06:44 +0100 [thread overview]
Message-ID: <20081125200644.GA7128@uranus.ravnborg.org> (raw)
Almost all other architectures has moved over to arch/$ARCH/include
Are you planning to do so for mn10300 for next merge window?
Remaining ones: frv, h8300, m32r, m68k and mn10300
The other are done or have patches queued for next merge window to do so.
Can I be of any help?
Sam
next reply other threads:[~2008-11-25 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 20:06 Sam Ravnborg [this message]
2008-11-25 20:22 ` mn10300: Any plans to introduce arch/mn10300/include? Sam Ravnborg
2008-12-01 13:01 ` David Howells
2008-12-01 13:13 ` 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=20081125200644.GA7128@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=dhowells@redhat.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=yasutake.koichi@jp.panasonic.com \
/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