From: Sasha Levin <sashal@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] tools/lib/traceevent: Fix processing of dereferenced args in bprintk events
Date: Mon, 10 Dec 2018 18:03:32 -0500 [thread overview]
Message-ID: <20181210230332.GH97256@sasha-vm> (raw)
In-Reply-To: <20181210162515.4a10d827@gandalf.local.home>
On Mon, Dec 10, 2018 at 04:25:15PM -0500, Steven Rostedt wrote:
>On Mon, 10 Dec 2018 21:09:20 +0000
>Sasha Levin <sashal@kernel.org> wrote:
>
>> Hi,
>>
>> [This is an automated email]
>>
>> This commit has been processed because it contains a "Fixes:" tag,
>> fixing commit: .
>>
>> The bot has tested the following trees: v4.19.8, v4.14.87, v4.9.144, v4.4.166, v3.18.128,
>>
>> v4.19.8: Build OK!
>> v4.14.87: Failed to apply! Possible dependencies:
>> 37db96bb4962 ("tools lib traceevent: Handle new pointer processing of bprint strings")
>
>Bah, I cut and pasted incorrectly the sha1. I had:
>
>7db96bb49629 (chopped off the 3)
You tricked my bot :)
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-12-10 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 18:45 [PATCH] tools/lib/traceevent: Fix processing of dereferenced args in bprintk events Steven Rostedt
2018-12-10 18:48 ` Arnaldo Carvalho de Melo
2018-12-10 21:26 ` Steven Rostedt
2018-12-11 12:29 ` Arnaldo Carvalho de Melo
[not found] ` <20181210210921.A4C862084C@mail.kernel.org>
2018-12-10 21:25 ` Steven Rostedt
2018-12-10 23:03 ` Sasha Levin [this message]
2018-12-20 18:00 ` [tip:perf/core] tools lib traceevent: " tip-bot for Steven Rostedt (VMware)
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=20181210230332.GH97256@sasha-vm \
--to=sashal@kernel.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@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 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.