From: Steven Rostedt <rostedt@goodmis.org>
To: Russ Dill <Russ.Dill@ti.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ktest.pl: Fix combined usage of BISECT_REVERSE and BISECT_SKIP
Date: Wed, 25 Apr 2012 07:09:40 -0400 [thread overview]
Message-ID: <1335352180.28106.151.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4F9776B4.60001@ti.com>
On Tue, 2012-04-24 at 20:59 -0700, Russ Dill wrote:
> BTW, I can across an additional problem that I'm not sure how to solve.
> I'm using PRE_BUILD and POST_BUILD to apply a patch during a bisect. As
> soon as the bisect hits a tree where the patch applies, the module
> tar-up fails. The kernel version (and module path) has a '-dirty' but
> ktest.pl is calling its get_version after POST_BUILD when the tree is clean.
I'm aware of this issue, as I hit this bug myself. I have some patches
that fix it, but they are currently ugly. I'm working on a better fix.
Thanks,
-- Steve
next prev parent reply other threads:[~2012-04-25 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 23:08 [PATCH] " Russ Dill
2012-04-23 23:15 ` [PATCH v2] ktest.pl: " Russ Dill
2012-04-24 0:55 ` Steven Rostedt
2012-04-25 3:59 ` Russ Dill
2012-04-25 11:09 ` Steven Rostedt [this message]
2012-04-24 2:43 ` [PATCH v3] " Russ Dill
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=1335352180.28106.151.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=Russ.Dill@ti.com \
--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®