From: Dave Jones <davej@redhat.com>
To: Ildar Muslukhov <ildarm@google.com>
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH] Added parameter that controls which taint flag causes trinity to stop.
Date: Tue, 24 Sep 2013 12:15:19 -0400 [thread overview]
Message-ID: <20130924161519.GA10098@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1309231938120.18899@ildarm-linux.kir.corp.google.com>
On Mon, Sep 23, 2013 at 07:41:14PM -0700, Ildar Muslukhov wrote:
>
> Hello Everyone,
>
> This is reworked patch for the parameter that allows to control which
> kernel taint flags causes trinity to stop. In particular, now the short
> parameter is -T (instead of -t) and flags has to be specified as literals
> (e.g., DIE, WARN, USER, etc.). All 13 supported flags are specified in
> README.
>
> Signed-off-by: Ildar Muslukhov <ildarm@google.com>
Applied. Watch out for your whitespace though..
$ git am ~/ildar
Applying: Added parameter that controls which taint flag causes trinity to stop.
/home/davej/src/git-trees/trinity/.git/rebase-apply/patch:158: indent with spaces.
toggle_taint_flag(TAINT_FORCED_MODULE);
/home/davej/src/git-trees/trinity/.git/rebase-apply/patch:160: indent with spaces.
toggle_taint_flag(TAINT_UNSAFE_SMP);
/home/davej/src/git-trees/trinity/.git/rebase-apply/patch:162: indent with spaces.
toggle_taint_flag(TAINT_FORCED_RMMOD);
/home/davej/src/git-trees/trinity/.git/rebase-apply/patch:164: indent with spaces.
toggle_taint_flag(TAINT_MACHINE_CHECK);
/home/davej/src/git-trees/trinity/.git/rebase-apply/patch:166: indent with spaces.
toggle_taint_flag(TAINT_BAD_PAGE);
warning: squelched 7 whitespace errors
warning: 12 lines applied after fixing whitespace errors.
There's a commit hook that fixes things up when I commit them, but it's better
if I don't even see that spew when I apply diffs ;)
thanks,
Dave
prev parent reply other threads:[~2013-09-24 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 2:41 [PATCH] Added parameter that controls which taint flag causes trinity to stop Ildar Muslukhov
2013-09-24 16:15 ` Dave Jones [this message]
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=20130924161519.GA10098@redhat.com \
--to=davej@redhat.com \
--cc=ildarm@google.com \
--cc=trinity@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