From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Glenn Washburn <development@efficientek.com>,
Kieran Bingham <kbingham@kernel.org>,
linux-um <linux-um@lists.infradead.org>,
Richard Weinberger <richard@nod.at>,
Johannes Berg <johannes@sipsolutions.net>,
Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
Subject: Re: [PATCH v2 0/2] GDB: Support getting current task struct in UML
Date: Thu, 16 Feb 2023 14:40:01 -0800 [thread overview]
Message-ID: <20230216144001.e1a9dea15a6c4f93b7b8a442@linux-foundation.org> (raw)
In-Reply-To: <8a22d84e-5cf4-bf41-220e-dc5e48fb2fc3@siemens.com>
On Thu, 16 Feb 2023 08:51:52 +0100 Jan Kiszka <jan.kiszka@siemens.com> wrote:
> On 16.02.23 08:37, Glenn Washburn wrote:
> > Added suggestions from Jan.
> >
> > Glenn
> >
> > Glenn Washburn (2):
> > scripts/gdb: Correct indentation in get_current_task
> > scripts/gdb: Support getting current task struct in UML
> >
>
> ...
>
> Reviewed-by: Jan Kiszka <jan.kiszka@siemens.com>
>
Thanks, but I'm not subscribed to linux-um and my usual
get-it-from-lkml didn't work.
Could we please have a resend, with a cc to linux-kernel?
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-02-16 22:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 7:37 [PATCH v2 0/2] GDB: Support getting current task struct in UML Glenn Washburn
2023-02-18 1:11 ` Glenn Washburn
2023-02-18 1:11 ` Glenn Washburn
2023-02-16 7:37 ` [PATCH v2 1/2] scripts/gdb: Correct indentation in get_current_task Glenn Washburn
2023-02-18 1:11 ` Glenn Washburn
2023-02-18 1:11 ` Glenn Washburn
2023-02-16 7:37 ` [PATCH v2 2/2] scripts/gdb: Support getting current task struct in UML Glenn Washburn
2023-02-18 1:11 ` Glenn Washburn
2023-02-18 1:11 ` Glenn Washburn
2023-02-16 7:51 ` [PATCH v2 0/2] GDB: " Jan Kiszka
2023-02-16 22:40 ` Andrew Morton [this message]
2023-02-16 22:54 ` Richard Weinberger
2023-02-16 23:33 ` Andrew Morton
2023-02-17 10:14 ` Geert Uytterhoeven
2023-02-17 21:56 ` Glenn Washburn
2023-02-17 22:21 ` Andrew Morton
2023-02-23 21:14 ` Andrew Morton
2023-02-23 21:14 ` Andrew Morton
2023-02-26 6:47 ` Glenn Washburn
2023-02-26 6:47 ` Glenn Washburn
2023-02-26 19:35 ` Andrew Morton
2023-02-26 19:35 ` Andrew Morton
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=20230216144001.e1a9dea15a6c4f93b7b8a442@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=development@efficientek.com \
--cc=jan.kiszka@siemens.com \
--cc=johannes@sipsolutions.net \
--cc=kbingham@kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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.