linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kieran Bingham <kieran@ksquared.org.uk>,
	akpm@linux-foundation.org, corbet@lwn.net
Cc: osandov@fb.com, n.borisov.lkml@gmail.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] scripts/gdb: Fixes for 4.7
Date: Wed, 29 Jun 2016 07:00:53 +0200	[thread overview]
Message-ID: <57735605.50006@siemens.com> (raw)
In-Reply-To: <1467127337-11135-1-git-send-email-kieran@bingham.xyz>

On 2016-06-28 17:22, Kieran Bingham wrote:
> Hi Andrew,
> 
> Please consider this series for integration into the current rc series.
> I had hoped to get this to you, with a fixed radix-tree, rather than a
> reverted one. Alas, time has gone against me, and we are nearing the end
> of the window - so having discussed with Jan, we felt it best to simply
> revert the feature for this release.
> 
> Aside from the revert, we have four fairly minor fixups.
> 
> Kieran Bingham (4):
>   scripts/gdb: silence 'nothing to do' message
>   scripts/gdb: rebuild constants.py on dependancy change
>   Revert "scripts/gdb: add a Radix Tree Parser"
>   Revert "scripts/gdb: add documentation example for radix tree"
> 
> Nikolay Borisov (1):
>   scripts/gdb: Perform path expansion to lx-symbol's arguments
> 
> Omar Sandoval (1):
>   scripts/gdb: add constants.py to .gitignore
> 
>  Documentation/gdb-kernel-debugging.txt | 21 --------
>  scripts/gdb/linux/.gitignore           |  1 +
>  scripts/gdb/linux/Makefile             |  6 ++-
>  scripts/gdb/linux/constants.py.in      |  7 ---
>  scripts/gdb/linux/radixtree.py         | 97 ----------------------------------
>  scripts/gdb/linux/symbols.py           |  2 +-
>  scripts/gdb/vmlinux-gdb.py             |  1 -
>  7 files changed, 6 insertions(+), 129 deletions(-)
>  delete mode 100644 scripts/gdb/linux/radixtree.py
> 

For all:
Acked-by: Jan Kiszka <jan.kiszka@siemens.com>

Thanks!
Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2016-06-29  5:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 15:22 [PATCH 0/6] scripts/gdb: Fixes for 4.7 Kieran Bingham
2016-06-28 15:22 ` [PATCH 1/6] scripts/gdb: silence 'nothing to do' message Kieran Bingham
2016-06-28 15:22 ` [PATCH 2/6] scripts/gdb: rebuild constants.py on dependancy change Kieran Bingham
2016-06-28 15:22 ` [PATCH 3/6] scripts/gdb: add constants.py to .gitignore Kieran Bingham
2016-06-28 15:22 ` [PATCH 4/6] scripts/gdb: Perform path expansion to lx-symbol's arguments Kieran Bingham
2016-06-28 15:22 ` [PATCH 5/6] Revert "scripts/gdb: add a Radix Tree Parser" Kieran Bingham
2016-06-28 15:22 ` [PATCH 6/6] Revert "scripts/gdb: add documentation example for radix tree" Kieran Bingham
2016-06-29  5:00 ` Jan Kiszka [this message]
2016-07-11 10:17   ` [PATCH 0/6] scripts/gdb: Fixes for 4.7 Kieran Bingham
2016-07-11 19:53     ` Andrew Morton
2016-07-11 20:15       ` Kieran Bingham

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=57735605.50006@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=kieran@ksquared.org.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n.borisov.lkml@gmail.com \
    --cc=osandov@fb.com \
    /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;
as well as URLs for NNTP newsgroup(s).