From: Ingo Molnar <mingo@kernel.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: tip-bot for Josh Poimboeuf <tipbot@zytor.com>,
linux-tip-commits@vger.kernel.org, peterz@infradead.org,
koct9i@gmail.com, torvalds@linux-foundation.org,
alexander.levin@verizon.com, linux-kernel@vger.kernel.org,
kirill@shutemov.name, hpa@zytor.com, tglx@linutronix.de
Subject: Re: [tip:x86/urgent] tools/decode_stacktrace.sh: Fix address line detection on x86
Date: Tue, 29 Nov 2016 14:20:23 +0100 [thread overview]
Message-ID: <20161129132023.GA24321@gmail.com> (raw)
In-Reply-To: <20161129130646.j2jyop27snukkdzy@treble>
* Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> Hi tip-bot,
>
> On Mon, Nov 28, 2016 at 11:13:15PM -0800, tip-bot for Josh Poimboeuf wrote:
> > Commit-ID: 8e8d8725d46d93ceffd3e708d905bc101a1905b5
> > Gitweb: http://git.kernel.org/tip/8e8d8725d46d93ceffd3e708d905bc101a1905b5
> > Author: Josh Poimboeuf <jpoimboe@redhat.com>
> > AuthorDate: Mon, 28 Nov 2016 17:06:35 -0600
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Tue, 29 Nov 2016 08:10:05 +0100
> >
> > tools/decode_stacktrace.sh: Fix address line detection on x86
>
> It's actually in the scripts subdir, so: s/tools/scripts/
So that was conscious - it might be in 'scripts' but it is really a tool!
No strong feelings either way.
> Also, while it should be harmless for this to be in 'urgent', I think it
> isn't necessary because it fixes a commit which is currently only in
> tip.
I missed that.
Ok, I rebased it over into tip:x86/asm and fixed the title as well while at it.
Thanks,
Ingo
next prev parent reply other threads:[~2016-11-29 13:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 14:51 [PATCH 0/4] x86: fix kernel address printk exposures Josh Poimboeuf
2016-10-25 14:51 ` [PATCH 1/4] scripts/faddr2line: fix "size mismatch" error Josh Poimboeuf
2016-10-26 5:39 ` [tip:x86/asm] scripts/faddr2line: Fix " tip-bot for Josh Poimboeuf
2016-10-25 14:51 ` [PATCH 2/4] x86/dumpstack: remove kernel text addresses from stack dump Josh Poimboeuf
2016-10-26 5:40 ` [tip:x86/asm] x86/dumpstack: Remove " tip-bot for Josh Poimboeuf
2016-11-25 12:26 ` [PATCH 2/4] x86/dumpstack: remove " Kirill A. Shutemov
2016-11-28 20:49 ` Josh Poimboeuf
2016-11-28 22:27 ` Kirill A. Shutemov
2016-11-28 23:06 ` [PATCH] decode_stacktrace: fix address line detection on x86 Josh Poimboeuf
2016-11-29 7:13 ` [tip:x86/urgent] tools/decode_stacktrace.sh: Fix " tip-bot for Josh Poimboeuf
2016-11-29 13:06 ` Josh Poimboeuf
2016-11-29 13:20 ` Ingo Molnar [this message]
2016-11-29 13:24 ` [tip:x86/asm] scripts/decode_stacktrace.sh: " tip-bot for Josh Poimboeuf
2016-10-25 14:51 ` [PATCH 3/4] x86/dumpstack: remove raw stack dump Josh Poimboeuf
2016-10-26 5:40 ` [tip:x86/asm] x86/dumpstack: Remove " tip-bot for Josh Poimboeuf
2016-10-25 14:51 ` [PATCH 4/4] mm: remove kernel address exposure in free_reserved_area() Josh Poimboeuf
2016-10-26 5:41 ` [tip:x86/asm] mm/page_alloc: Remove " tip-bot for Josh Poimboeuf
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=20161129132023.GA24321@gmail.com \
--to=mingo@kernel.org \
--cc=alexander.levin@verizon.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=kirill@shutemov.name \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tipbot@zytor.com \
--cc=torvalds@linux-foundation.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