From: Glenn Washburn <development@efficientek.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Richard Weinberger <richard@nod.at>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
linux-um <linux-um@lists.infradead.org>,
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: Fri, 17 Feb 2023 15:56:43 -0600 [thread overview]
Message-ID: <20230217155643.1c1b0b76@crass-HP-ZBook-15-G2> (raw)
In-Reply-To: <CAMuHMdWdQH=o9XNAj4YpTA8G7JMKPe+CJSCG2bRf_6H-u50PZg@mail.gmail.com>
On Fri, 17 Feb 2023 11:14:01 +0100
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Hi Andrew,
>
> On Fri, Feb 17, 2023 at 12:33 AM Andrew Morton
> <akpm@linux-foundation.org> wrote:
> > On Thu, 16 Feb 2023 23:54:38 +0100 (CET) Richard Weinberger
> > <richard@nod.at> wrote:
> > > ----- Ursprüngliche Mail -----
> > > > Von: "Andrew Morton" <akpm@linux-foundation.org>
> > > > 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?
> > >
> > > You can also get the patches in mbox format from:
> > > https://patchwork.ozlabs.org/project/linux-um/list/?series=342212
>
> And from there, you can get the Message-IDs, and use lore:
> https://lore.kernel.org/r/683d10e752cd4852ac62ef3cc3e9a6972a017bdf.1676532759.git.development@efficientek.com
> or b4:
> b4 mbox
> 683d10e752cd4852ac62ef3cc3e9a6972a017bdf.1676532759.git.development@efficientek.com
> b4 am
> 683d10e752cd4852ac62ef3cc3e9a6972a017bdf.1676532759.git.development@efficientek.com
>
> > Thanks, but..
> >
> > - Can't do reply-to-all if I have comments
> > - Can't collect people's followup acks and review comments
> > - No Link tag
Ok, so do I need to resend after all? And anther point in need of
clarification, regardless of subsystem or area of source, when sending
patches, should I always cc to linux-kernel?
Glenn
_______________________________________________
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-17 21:57 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
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 [this message]
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=20230217155643.1c1b0b76@crass-HP-ZBook-15-G2 \
--to=development@efficientek.com \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@kot-begemot.co.uk \
--cc=geert@linux-m68k.org \
--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.