From: Andrew Morton <akpm@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: linux-arch@vger.kernel.org, sam@ravnborg.org
Subject: Re: + create-arch-kconfig.patch added to -mm tree
Date: Thu, 15 Nov 2007 18:07:22 -0800 [thread overview]
Message-ID: <20071115180722.8ae4b285.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071116015730.GA16953@Krystal>
On Thu, 15 Nov 2007 20:57:30 -0500 Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> I have an updated patchset for these 4 instrumentation menu patches,
> following Sam Ravnborg's comments (using ARCH_HAS_* instead of
> ARCH_SUPPORTS_*). I was planning to send them with my next patch round.
>
> create-arch-kconfig.patch
> add-arch_supports_oprofile.patch
> add-arch_supports_kprobes.patch
> move-kconfiginstrumentation-to-arch-kconfig-and-init-kconfig.patch
So I've fixed all the rejects, fixed it all up for the arch/x86/Kconfig
churn, merged another patchset which depends on this one and now I'm told
that they need to be updated?
Sigh. Normally I know not to look at a Mathieu patch until it hits version 37,
but I wanted to merge
kprobes-indicate-kretprobe-support-in-arch-arch-kconfig.patch and
kprobes-build-kretprobe-samples-only-if-arch-supports-kretprobes.patch
which depend on these patches.
It seems that they will now break. afacit I'll need to do
s/CONFIG_ARCH_SUPPORTS_KRETPROBES/CONFIG_ARCH_HAD_KRETPROBES/ on those
patches.
Please send updated versions of these four asap?
next prev parent reply other threads:[~2007-11-16 2:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 22:27 + create-arch-kconfig.patch added to -mm tree akpm
2007-11-16 1:57 ` Mathieu Desnoyers
2007-11-16 2:07 ` Andrew Morton [this message]
2007-11-16 2:14 ` Mathieu Desnoyers
2007-11-16 8:24 ` Russell King
2007-11-16 8:20 ` Russell King
2007-11-16 13:53 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2007-11-16 23:03 akpm
2007-12-12 5:38 akpm
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=20071115180722.8ae4b285.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=sam@ravnborg.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 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.