From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Al Viro <viro@www.linux.org.uk>,
geert@linux-m68k.org, torvalds@osdl.org,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] (18/22) task_thread_info - part 2/4
Date: Thu, 25 Aug 2005 14:59:33 +0100 [thread overview]
Message-ID: <20050825135933.GA14448@infradead.org> (raw)
In-Reply-To: <20050825130738.GQ9322@parcelfarce.linux.theplanet.co.uk>
On Thu, Aug 25, 2005 at 02:07:38PM +0100, Al Viro wrote:
> Fine, as long as that merge is done before your s/thread_info/stack/ patches.
> It should be the first step before doing 200Kb worth of cosmetical stuff
> that affects every architecture out there, not something that depends on
> it done.
>
> There's also a question of having mainline build and work on the architecture
> in question, which obviously is not something you care about - this hairball
> had been sitting in m68k CVS for how long? Since 2.5.60-something, with
> zero efforts to resolve it, right? And mainline kernel didn't even build,
> let alone work since that moment.
Yup. Let's get m68k into buildable shape for 2.6.13 with Al's minimal
patches, and if you have further improvements over that submit them as
split up patches through the usual channels. Having all architectures
actually build and work from mainline is really important to have
useful kernel package in distributions.
next prev parent reply other threads:[~2005-08-25 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 5:25 Al Viro
2005-08-25 8:41 ` Geert Uytterhoeven
2005-08-25 13:12 ` Al Viro
2005-08-25 9:15 ` Roman Zippel
2005-08-25 13:07 ` Al Viro
2005-08-25 13:59 ` Christoph Hellwig [this message]
2005-08-25 14:15 ` Roman Zippel
2005-08-25 14:33 ` Geert Uytterhoeven
2005-08-25 14:41 ` Al Viro
2005-08-25 15:30 ` Roman Zippel
2005-08-25 14:10 ` Roman Zippel
2005-08-25 14:36 ` Al Viro
2005-08-25 15:20 ` Roman Zippel
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=20050825135933.GA14448@infradead.org \
--to=hch@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=viro@www.linux.org.uk \
--cc=zippel@linux-m68k.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®