From: Mikael Pettersson <mikpe@csd.uu.se>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.6.11-mm3] perfctr ia32 syscalls on x86-64 fix
Date: Sun, 13 Mar 2005 12:56:11 +0100 (MET) [thread overview]
Message-ID: <200503131156.j2DBuBFv015778@harpo.it.uu.se> (raw)
On Sat, 12 Mar 2005 21:55:49 -0800, Andrew Morton wrote:
>It would be nice to start folding these patches together a bit to reduce
>such problems, but that's rather non-trivial because there is no way to
>simply join these patches together which maintains a sensible sequencing.
>
>If we're going to do anything then it's either a major refactoring, or
>simply wham the entire feature into a single diff. That diff could then be
>split into four patches: core, ppc, x86 and x86_64. We would lose the
>layering between ye olde perfctr, the inheritance implementation, the syfs
>API, etc. I could live with that.
>
>What do you think?
At my end there is already just "the current version"
(with history in cvs) so merging is fine with me.
/Mikael
next reply other threads:[~2005-03-13 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 11:56 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 23:26 Mikael Pettersson
2005-03-13 5:55 ` 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=200503131156.j2DBuBFv015778@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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®