From: Ingo Molnar <mingo@elte.hu>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
davem@davemloft.net, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Use __u64 in aligned_u64's definition
Date: Fri, 4 Jan 2008 12:03:33 +0100 [thread overview]
Message-ID: <20080104110333.GA26149@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0801022243450.14900@fbirervta.pbzchgretzou.qr>
* Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Jan 2 2008 13:42, Linus Torvalds wrote:
> >On Wed, 2 Jan 2008, Jan Engelhardt wrote:
> >>
> >> A cleanup. Or perhaps a precautionary change, should unsigned long
> >> long ever become something that is not 64-bit. It was intended for
> >> 2.6.25 actually. You don't take patches this early, do you?
> >
> >Yeah, no, I don't take patches early. I've considered setting up another
> >branch for early patches, but decided that I'm (a) lazy and (b) better off
> >encouraging people in the late -rc timeframe to just concentrate on the
> >-rc's, not the next version.
>
> Well you can also apply it right now, then it's done and life can go
> on.
which part of the "it's an unnecessary distraction" concept didnt you
understand? We are in -rc6 and all the codebase is in deep freeze. Delay
your patch to when the 2.6.25 merge window starts and life can go on.
Ingo
next prev parent reply other threads:[~2008-01-04 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 20:42 Jan Engelhardt
2008-01-02 20:52 ` Linus Torvalds
2008-01-02 21:28 ` Jan Engelhardt
2008-01-02 21:42 ` Linus Torvalds
2008-01-02 21:48 ` Jan Engelhardt
2008-01-04 11:03 ` Ingo Molnar [this message]
2008-01-04 11:25 ` Stefan Richter
2008-01-04 11:47 ` David Miller
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=20080104110333.GA26149@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome