From: Robin Holt <holt@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Stephane Eranian <eranian@frankl.hpl.hp.com>,
linux-kernel@vger.kernel.org, eranian@hpl.hp.com
Subject: Re: [PATCH 02/22] 2.6.22-rc3 perfmon2 : generic kernel modifications
Date: Wed, 30 May 2007 06:34:03 -0500 [thread overview]
Message-ID: <20070530113403.GA14480@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <20070530004658.732451ad.sfr@canb.auug.org.au>
On Wed, May 30, 2007 at 12:46:58AM +1000, Stephen Rothwell wrote:
> On Tue, 29 May 2007 06:48:16 -0700 Stephane Eranian <eranian@frankl.hpl.hp.com> wrote:
> >
> > Only in linux-2.6.22/Documentation: perfmon2.txt
>
> Did part of the patch go missing?
>
> > diff --exclude=.git -urp --exclude-from=/tmp/excl315935 linux-2.6.22.base/Makefile linux-2.6.22/Makefile
> > --- linux-2.6.22.base/Makefile 2007-05-29 03:17:15.000000000 -0700
> > +++ linux-2.6.22/Makefile 2007-05-29 03:24:14.000000000 -0700
> > @@ -553,7 +553,7 @@ export mod_strip_cmd
> >
> >
> > ifeq ($(KBUILD_EXTMOD),)
> > -core-y += kernel/ mm/ fs/ ipc/ security/ crypto/ block/
> > +core-y += kernel/ mm/ fs/ ipc/ security/ crypto/ block/ perfmon/
>
> This should go near the end of the patch set so that the kernel will
> build at each step (if at all possible).
>
> Seeing as what is missing below, naybe you should reorder the patch set
> so that the generic changes are at the end i.e. introduce all the new
> files and then wire them into the current ifrastructure.
That breaks git-bisect. Just introducing new text, but not actually using
it makes it appear to somebody using git-bisect to identify the source of
a problem as though all the changes came in at the same time. Bad idea.
Thanks,
Robin
next prev parent reply other threads:[~2007-05-30 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 13:48 Stephane Eranian
2007-05-29 14:46 ` Stephen Rothwell
2007-05-30 11:34 ` Robin Holt [this message]
2007-05-30 13:42 ` Stephen Rothwell
2007-05-30 13:56 ` Stephane Eranian
2007-06-04 15:13 ` David Rientjes
2007-06-07 8:18 ` Stephane Eranian
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=20070530113403.GA14480@lnx-holt.americas.sgi.com \
--to=holt@sgi.com \
--cc=eranian@frankl.hpl.hp.com \
--cc=eranian@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®