From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: harvey.harrison@gmail.com, mingo@elte.hu, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 19/22] x86: use the new byteorder headers
Date: Tue, 12 Aug 2008 23:05:11 -0700 [thread overview]
Message-ID: <20080812230511.6182a084.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080812.225924.62357936.davem@davemloft.net>
On Tue, 12 Aug 2008 22:59:24 -0700 (PDT) David Miller <davem@davemloft.net> wrote:
> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Tue, 12 Aug 2008 22:56:12 -0700
>
> > I'll drop them all. Do you have a cross-compiler suite there?
>
> I think Harvey needs a mentor which can help him learn how to properly
> build validate his patches before he submits them, and how to not mix
> things up by, for example, validating the build with patches applied
> that won't be submitted etc.
>
> Every time I integrate these byteorder patches directly for networking
> or sparc, it tends to be a build regression nightmare.
>
> I think Andrew has hit 3 already with this patch series, quite an
> accomplishment. :-/
heh. This is why I habitually wait until Harveypatches hit version 4.
Maybe I need to increment that a bit.
next prev parent reply other threads:[~2008-08-13 6:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 0:27 [PATCH 19/22] x86: use the new byteorder headers Harvey Harrison
2008-08-13 3:54 ` Andrew Morton
2008-08-13 4:05 ` [PATCH] tipc: Use the appropriate swab helper rather than an internal helper Harvey Harrison
2008-08-13 4:20 ` Andrew Morton
2008-08-13 4:23 ` Harvey Harrison
2008-08-13 9:32 ` David Miller
2008-08-13 5:56 ` [PATCH 19/22] x86: use the new byteorder headers Andrew Morton
2008-08-13 5:59 ` David Miller
2008-08-13 6:05 ` Andrew Morton [this message]
2008-08-13 6:02 ` Andrew Morton
2008-08-13 6:07 ` Harvey Harrison
2008-08-13 6:47 ` Andrew Morton
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=20080812230511.6182a084.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.