From: Ritesh Harjani <riteshh@linux.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ritesh Harjani <riteshh@linux.ibm.com>
Subject: [PATCHv2 0/2] scripts:gdb: Add few structs info in gdb scripts
Date: Tue, 18 Aug 2020 15:04:59 +0530 [thread overview]
Message-ID: <cover.1597742951.git.riteshh@linux.ibm.com> (raw)
I was using these structs info internally in my gdb scripts.
So sending it out for merge to upstream.
Patch-2 is just adding some headers and improves spacing.
--
2.25.4
next reply other threads:[~2020-08-18 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 9:34 Ritesh Harjani [this message]
2020-08-18 9:35 ` [PATCHv2 1/2] proc: Add struct mount & struct super_block addr in lx-mounts command Ritesh Harjani
2020-08-18 9:35 ` [PATCHv2 2/2] tasks: Add headers and improve spacing format Ritesh Harjani
2020-08-18 9:51 ` [PATCHv2 0/2] scripts:gdb: Add few structs info in gdb scripts Jan Kiszka
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=cover.1597742951.git.riteshh@linux.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--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