From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, Greg Kurz <groug@kaod.org>
Subject: Re: [PULL 0/8] 9p queue 2021-07-05
Date: Mon, 05 Jul 2021 17:34:45 +0200 [thread overview]
Message-ID: <2066764.2AXzDdBHVr@silver> (raw)
In-Reply-To: <CAFEAcA-uHfJrJc9JcVRZ7x9WG1sY0C+zbC=m5gzyRdVG+TL49Q@mail.gmail.com>
On Montag, 5. Juli 2021 15:57:41 CEST Peter Maydell wrote:
> On Mon, 5 Jul 2021 at 12:24, Christian Schoenebeck
>
> <qemu_oss@crudebyte.com> wrote:
> > The following changes since commit 711c0418c8c1ce3a24346f058b001c4c5a2f0f81:
> > Merge remote-tracking branch 'remotes/philmd/tags/mips-20210702' into
> > staging (2021-07-04 14:04:12 +0100)>
> > are available in the Git repository at:
> > https://github.com/cschoenebeck/qemu.git tags/pull-9p-20210705
> >
> > for you to fetch changes up to 8d6cb100731c4d28535adbf2a3c2d1f29be3fef4:
> > 9pfs: reduce latency of Twalk (2021-07-05 13:03:16 +0200)
> >
> > ----------------------------------------------------------------
> > 9pfs: misc patches
> >
> > * Add link to 9p developer docs.
> >
> > * Fix runtime check whether client supplied relative path is the export
> >
> > root.
> >
> > * Performance optimization of Twalk requests.
> >
> > * Code cleanup.
>
> GPG tells me the key you signed this with has expired. Can you point
> me at a keyserver I can download an updated version of the key from,
> please?
>
> thanks
> -- PMM
Hi Peter,
I must have done something wrong when I sent out the updated, prolonged key
info couple weeks ago.
I just sent it out again to couple key servers now. They are all still the
same key IDs BTW, I just prolonged their expiration dates. Looks fine now:
https://keyserver.ubuntu.com/pks/lookup?search=qemu_oss%40crudebyte.com&op=vindex&fingerprint=on
http://pgp.mit.edu/pks/lookup?op=vindex&search=0x30DB47C3A012D5F4
https://github.com/cschoenebeck/qemu/releases/tag/pull-9p-20210705
sec# rsa4096/30DB47C3A012D5F4 2020-05-28 [SC] [expires: 2024-05-16]
ECAB1A4540141413BA38492630DB47C3A012D5F4
uid [ultimate] Christian Schoenebeck <qemu_oss@crudebyte.com>
ssb rsa4096/C64F2382FC0F4C5E 2020-05-28 [E] [expires: 2022-11-08]
ssb rsa4096/34C2B58765A47395 2020-05-28 [S] [expires: 2022-11-08]
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2021-07-05 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 11:13 [PULL 0/8] 9p queue 2021-07-05 Christian Schoenebeck
2021-07-05 11:13 ` [PULL 5/8] 9pfs: drop fid_to_qid() Christian Schoenebeck
2021-07-05 11:13 ` [PULL 6/8] 9pfs: replace not_same_qid() by same_stat_id() Christian Schoenebeck
2021-07-05 11:13 ` [PULL 2/8] 9pfs: simplify v9fs_walk() Christian Schoenebeck
2021-07-05 11:13 ` [PULL 8/8] 9pfs: reduce latency of Twalk Christian Schoenebeck
2021-07-05 11:13 ` [PULL 4/8] 9pfs: capture root stat Christian Schoenebeck
2021-07-05 11:13 ` [PULL 3/8] 9pfs: fix not_same_qid() Christian Schoenebeck
2021-07-05 11:13 ` [PULL 7/8] 9pfs: drop root_qid Christian Schoenebeck
2021-07-05 11:13 ` [PULL 1/8] 9pfs: add link to 9p developer docs Christian Schoenebeck
2021-07-05 13:57 ` [PULL 0/8] 9p queue 2021-07-05 Peter Maydell
2021-07-05 15:34 ` Christian Schoenebeck [this message]
2021-07-05 19:03 ` Peter Maydell
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=2066764.2AXzDdBHVr@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).