From: Andrew Morton <akpm@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: torvalds@linux-foundation.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/2] byteorder: add a new include/linux/swab.h to define byteswapping functions
Date: Thu, 17 Jul 2008 15:59:53 -0700 [thread overview]
Message-ID: <20080717155953.5cddc48d.akpm@linux-foundation.org> (raw)
In-Reply-To: <1216148509.6610.14.camel@brick>
On Tue, 15 Jul 2008 12:01:49 -0700
Harvey Harrison <harvey.harrison@gmail.com> wrote:
> Collect the implementations from include/linux/byteorder/swab.h, swabb.h
> in swab.h
I'm afraid I've been basically ignoring the storm of byteorder and
related patches simply because I do not have a large enough brain to
work out wth is going on.
I get the impression that there's a great storm of random patches, some
of which are repeats, with a distressing number of updates all with no
overall plan. Probably I'm wrong about that, but making it all not
_look_ like that would really help.
So ho hum. I merged these two into -mm, at the tail of the queue, in a
new "byteorder" "tree", probably for 2.6.28. We could bump them up
into 2.6.27-rc1 if that would help merging followup stuff out into the
subsystem trees during the 2.6.27-rcX cycle.
But please be aware that this ongoing patchstorm is quite confusing
from where I sit, and I just haven't been able to justify expending all
the time which it seems that it requires for me to work out just what
the heck is going on.
So please, send the patches less frequently, in larger batches, after
lots of testing. Each series should have some overall theme which is
clearly explained in an easy-to-follow fashion.
Ta.
next prev parent reply other threads:[~2008-07-17 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 19:01 [PATCH 1/2] byteorder: add a new include/linux/swab.h to define byteswapping functions Harvey Harrison
2008-07-17 22:59 ` Andrew Morton [this message]
2008-07-17 23:23 ` Harvey Harrison
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=20080717155953.5cddc48d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-arch@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;
as well as URLs for NNTP newsgroup(s).