From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> To: Elliot Berman <quic_eberman@quicinc.com> Cc: Bjorn Andersson <quic_bjorande@quicinc.com>, Murali Nalajala <quic_mnalajal@quicinc.com>, Trilok Soni <quic_tsoni@quicinc.com>, Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>, Carl van Schaik <quic_cvanscha@quicinc.com>, Andy Gross <agross@kernel.org>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, Jassi Brar <jassisinghbrar@gmail.com>, linux-arm-kernel@lists.infradead.org, Mark Rutland <mark.rutland@arm.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Sudeep Holla <sudeep.holla@arm.com>, Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Arnd Bergmann <arnd@arndb.de>, devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 06/14] virt: gunyah: Add sysfs nodes Date: Fri, 30 Sep 2022 14:09:27 +0200 [thread overview] Message-ID: <Yzbcd0r768pRgRMr@kroah.com> (raw) In-Reply-To: <20220928195633.2348848-7-quic_eberman@quicinc.com> On Wed, Sep 28, 2022 at 12:56:25PM -0700, Elliot Berman wrote: > Add /sys/hypervisor support when detecting that Linux is running in a > Gunyah environment. Export the version of Gunyah which is reported via > the hyp_identify hypercall. > > Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> > --- > .../ABI/testing/sysfs-hypervisor-gunyah | 15 ++++ > MAINTAINERS | 1 + > drivers/virt/Makefile | 1 + > drivers/virt/gunyah/Makefile | 2 + > drivers/virt/gunyah/sysfs.c | 71 +++++++++++++++++++ > 5 files changed, 90 insertions(+) > create mode 100644 Documentation/ABI/testing/sysfs-hypervisor-gunyah > create mode 100644 drivers/virt/gunyah/Makefile > create mode 100644 drivers/virt/gunyah/sysfs.c > > diff --git a/Documentation/ABI/testing/sysfs-hypervisor-gunyah b/Documentation/ABI/testing/sysfs-hypervisor-gunyah > new file mode 100644 > index 000000000000..7d74e74e9edd > --- /dev/null > +++ b/Documentation/ABI/testing/sysfs-hypervisor-gunyah > @@ -0,0 +1,15 @@ > +What: /sys/hypervisor/gunyah/api > +Date: October 2022 > +KernelVersion: 6.1 > +Contact: linux-arm-msm@vger.kernel.org > +Description: If running under Gunyah: > + The Gunyah API version. What does this version mean? What format is it in? > + > +What: /sys/hypervisor/gunyah/variant > +Date: October 2022 > +KernelVersion: 6.1 > +Contact: linux-arm-msm@vger.kernel.org > +Description: If running under Gunyah: > + Reports the build variant of Gunyah: > + The open source build of Gunyah will report "81". > + The Qualcomm build of Gunyah will report "72". So there are only 2 versions variants? What happens when you get a third? And why the odd numbers? What will userspace do with this information and what tool will parse it? > diff --git a/MAINTAINERS b/MAINTAINERS > index feafac12db35..a26e67ef36b4 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -8885,6 +8885,7 @@ M: Elliot Berman <quic_eberman@quicinc.com> > M: Murali Nalajala <quic_mnalajal@quicinc.com> > L: linux-arm-msm@vger.kernel.org > S: Supported > +F: Documentation/ABI/testing/sysfs-hypervisor-gunyah > F: Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml > F: Documentation/virt/gunyah/ > F: arch/arm64/gunyah/ > diff --git a/drivers/virt/Makefile b/drivers/virt/Makefile > index 093674e05c40..10b87f934730 100644 > --- a/drivers/virt/Makefile > +++ b/drivers/virt/Makefile > @@ -11,3 +11,4 @@ obj-$(CONFIG_NITRO_ENCLAVES) += nitro_enclaves/ > obj-$(CONFIG_ACRN_HSM) += acrn/ > obj-$(CONFIG_EFI_SECRET) += coco/efi_secret/ > obj-$(CONFIG_SEV_GUEST) += coco/sev-guest/ > +obj-$(CONFIG_GUNYAH) += gunyah/ > diff --git a/drivers/virt/gunyah/Makefile b/drivers/virt/gunyah/Makefile > new file mode 100644 > index 000000000000..e15f16c17142 > --- /dev/null > +++ b/drivers/virt/gunyah/Makefile > @@ -0,0 +1,2 @@ > +gunyah-y += sysfs.o > +obj-$(CONFIG_GUNYAH) += gunyah.o > diff --git a/drivers/virt/gunyah/sysfs.c b/drivers/virt/gunyah/sysfs.c > new file mode 100644 > index 000000000000..ec11510cbece > --- /dev/null > +++ b/drivers/virt/gunyah/sysfs.c > @@ -0,0 +1,71 @@ > +// SPDX-License-Identifier: GPL-2.0-only > +/* > + * Copyright (c) 2022 Qualcomm Innovation Center, Inc. All rights reserved. > + */ > + > +#define pr_fmt(fmt) "gunyah: " fmt > + > +#include <linux/kobject.h> > +#include <linux/module.h> > +#include <linux/printk.h> > +#include <linux/init.h> > +#include <asm-generic/gunyah.h> > + > +static struct gh_hypercall_hyp_identify_resp gunyah_api; > + > +static ssize_t api_show(struct kobject *kobj, struct kobj_attribute *attr, char *buffer) > +{ > + return sysfs_emit(buffer, "%d\n", (int)GH_API_INFO_API_VERSION(gunyah_api.api_info)); > +} > +static struct kobj_attribute api_attr = __ATTR_RO(api); > + > +static ssize_t variant_show(struct kobject *kobj, struct kobj_attribute *attr, char *buffer) > +{ > + return sysfs_emit(buffer, "%d\n", (int)GH_API_INFO_VARIANT(gunyah_api.api_info)); > +} > +static struct kobj_attribute variant_attr = __ATTR_RO(variant); > + > +static struct attribute *gunyah_attrs[] = { > + &api_attr.attr, > + &variant_attr.attr, > + NULL > +}; > + > +static const struct attribute_group gunyah_group = { > + .name = "gunyah", > + .attrs = gunyah_attrs, > +}; > + > +static int __init gunyah_init(void) > +{ > + u32 uid[4]; > + > + gh_hypercall_get_uid(uid); No error checking? > + > + if (!(gh_uid_matches(GUNYAH, uid) || gh_uid_matches(QC_HYP, uid))) > + return 0; > + > + gh_hypercall_hyp_identify(&gunyah_api); > + > + if (GH_API_INFO_API_VERSION(gunyah_api.api_info) != 1) { > + pr_warn("Unrecognized gunyah version: %llu. Currently supported: 1\n", > + GH_API_INFO_API_VERSION(gunyah_api.api_info)); Shouldn't the "1" be defined somewhere? > + return 0; > + } > + > + pr_notice("Running under Gunyah hypervisor %llx/v%lld\n", > + GH_API_INFO_VARIANT(gunyah_api.api_info), > + GH_API_INFO_API_VERSION(gunyah_api.api_info)); When kernel code is working properly, it is quiet. What is this going to be used for? thanks, greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> To: Elliot Berman <quic_eberman@quicinc.com> Cc: Bjorn Andersson <quic_bjorande@quicinc.com>, Murali Nalajala <quic_mnalajal@quicinc.com>, Trilok Soni <quic_tsoni@quicinc.com>, Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>, Carl van Schaik <quic_cvanscha@quicinc.com>, Andy Gross <agross@kernel.org>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, Jassi Brar <jassisinghbrar@gmail.com>, linux-arm-kernel@lists.infradead.org, Mark Rutland <mark.rutland@arm.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Sudeep Holla <sudeep.holla@arm.com>, Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Arnd Bergmann <arnd@arndb.de>, devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 06/14] virt: gunyah: Add sysfs nodes Date: Fri, 30 Sep 2022 14:09:27 +0200 [thread overview] Message-ID: <Yzbcd0r768pRgRMr@kroah.com> (raw) In-Reply-To: <20220928195633.2348848-7-quic_eberman@quicinc.com> On Wed, Sep 28, 2022 at 12:56:25PM -0700, Elliot Berman wrote: > Add /sys/hypervisor support when detecting that Linux is running in a > Gunyah environment. Export the version of Gunyah which is reported via > the hyp_identify hypercall. > > Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> > --- > .../ABI/testing/sysfs-hypervisor-gunyah | 15 ++++ > MAINTAINERS | 1 + > drivers/virt/Makefile | 1 + > drivers/virt/gunyah/Makefile | 2 + > drivers/virt/gunyah/sysfs.c | 71 +++++++++++++++++++ > 5 files changed, 90 insertions(+) > create mode 100644 Documentation/ABI/testing/sysfs-hypervisor-gunyah > create mode 100644 drivers/virt/gunyah/Makefile > create mode 100644 drivers/virt/gunyah/sysfs.c > > diff --git a/Documentation/ABI/testing/sysfs-hypervisor-gunyah b/Documentation/ABI/testing/sysfs-hypervisor-gunyah > new file mode 100644 > index 000000000000..7d74e74e9edd > --- /dev/null > +++ b/Documentation/ABI/testing/sysfs-hypervisor-gunyah > @@ -0,0 +1,15 @@ > +What: /sys/hypervisor/gunyah/api > +Date: October 2022 > +KernelVersion: 6.1 > +Contact: linux-arm-msm@vger.kernel.org > +Description: If running under Gunyah: > + The Gunyah API version. What does this version mean? What format is it in? > + > +What: /sys/hypervisor/gunyah/variant > +Date: October 2022 > +KernelVersion: 6.1 > +Contact: linux-arm-msm@vger.kernel.org > +Description: If running under Gunyah: > + Reports the build variant of Gunyah: > + The open source build of Gunyah will report "81". > + The Qualcomm build of Gunyah will report "72". So there are only 2 versions variants? What happens when you get a third? And why the odd numbers? What will userspace do with this information and what tool will parse it? > diff --git a/MAINTAINERS b/MAINTAINERS > index feafac12db35..a26e67ef36b4 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -8885,6 +8885,7 @@ M: Elliot Berman <quic_eberman@quicinc.com> > M: Murali Nalajala <quic_mnalajal@quicinc.com> > L: linux-arm-msm@vger.kernel.org > S: Supported > +F: Documentation/ABI/testing/sysfs-hypervisor-gunyah > F: Documentation/devicetree/bindings/firmware/gunyah-hypervisor.yaml > F: Documentation/virt/gunyah/ > F: arch/arm64/gunyah/ > diff --git a/drivers/virt/Makefile b/drivers/virt/Makefile > index 093674e05c40..10b87f934730 100644 > --- a/drivers/virt/Makefile > +++ b/drivers/virt/Makefile > @@ -11,3 +11,4 @@ obj-$(CONFIG_NITRO_ENCLAVES) += nitro_enclaves/ > obj-$(CONFIG_ACRN_HSM) += acrn/ > obj-$(CONFIG_EFI_SECRET) += coco/efi_secret/ > obj-$(CONFIG_SEV_GUEST) += coco/sev-guest/ > +obj-$(CONFIG_GUNYAH) += gunyah/ > diff --git a/drivers/virt/gunyah/Makefile b/drivers/virt/gunyah/Makefile > new file mode 100644 > index 000000000000..e15f16c17142 > --- /dev/null > +++ b/drivers/virt/gunyah/Makefile > @@ -0,0 +1,2 @@ > +gunyah-y += sysfs.o > +obj-$(CONFIG_GUNYAH) += gunyah.o > diff --git a/drivers/virt/gunyah/sysfs.c b/drivers/virt/gunyah/sysfs.c > new file mode 100644 > index 000000000000..ec11510cbece > --- /dev/null > +++ b/drivers/virt/gunyah/sysfs.c > @@ -0,0 +1,71 @@ > +// SPDX-License-Identifier: GPL-2.0-only > +/* > + * Copyright (c) 2022 Qualcomm Innovation Center, Inc. All rights reserved. > + */ > + > +#define pr_fmt(fmt) "gunyah: " fmt > + > +#include <linux/kobject.h> > +#include <linux/module.h> > +#include <linux/printk.h> > +#include <linux/init.h> > +#include <asm-generic/gunyah.h> > + > +static struct gh_hypercall_hyp_identify_resp gunyah_api; > + > +static ssize_t api_show(struct kobject *kobj, struct kobj_attribute *attr, char *buffer) > +{ > + return sysfs_emit(buffer, "%d\n", (int)GH_API_INFO_API_VERSION(gunyah_api.api_info)); > +} > +static struct kobj_attribute api_attr = __ATTR_RO(api); > + > +static ssize_t variant_show(struct kobject *kobj, struct kobj_attribute *attr, char *buffer) > +{ > + return sysfs_emit(buffer, "%d\n", (int)GH_API_INFO_VARIANT(gunyah_api.api_info)); > +} > +static struct kobj_attribute variant_attr = __ATTR_RO(variant); > + > +static struct attribute *gunyah_attrs[] = { > + &api_attr.attr, > + &variant_attr.attr, > + NULL > +}; > + > +static const struct attribute_group gunyah_group = { > + .name = "gunyah", > + .attrs = gunyah_attrs, > +}; > + > +static int __init gunyah_init(void) > +{ > + u32 uid[4]; > + > + gh_hypercall_get_uid(uid); No error checking? > + > + if (!(gh_uid_matches(GUNYAH, uid) || gh_uid_matches(QC_HYP, uid))) > + return 0; > + > + gh_hypercall_hyp_identify(&gunyah_api); > + > + if (GH_API_INFO_API_VERSION(gunyah_api.api_info) != 1) { > + pr_warn("Unrecognized gunyah version: %llu. Currently supported: 1\n", > + GH_API_INFO_API_VERSION(gunyah_api.api_info)); Shouldn't the "1" be defined somewhere? > + return 0; > + } > + > + pr_notice("Running under Gunyah hypervisor %llx/v%lld\n", > + GH_API_INFO_VARIANT(gunyah_api.api_info), > + GH_API_INFO_API_VERSION(gunyah_api.api_info)); When kernel code is working properly, it is quiet. What is this going to be used for? thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-30 12:09 UTC|newest] Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-28 19:56 [PATCH v4 00/14] Drivers for gunyah hypervisor Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 01/14] docs: gunyah: Introduce Gunyah Hypervisor Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-29 3:43 ` Bagas Sanjaya 2022-09-29 3:43 ` Bagas Sanjaya 2022-09-29 4:02 ` Elliot Berman 2022-09-29 4:02 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 02/14] dt-bindings: Add binding for gunyah hypervisor Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 03/14] gunyah: Common types and error codes for Gunyah hypercalls Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 04/14] arm64: smccc: Include alternative-macros.h Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 05/14] virt: gunyah: Add hypercalls to identify Gunyah Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 06/14] virt: gunyah: Add sysfs nodes Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-30 12:09 ` Greg Kroah-Hartman [this message] 2022-09-30 12:09 ` Greg Kroah-Hartman 2022-10-04 23:50 ` Elliot Berman 2022-10-04 23:50 ` Elliot Berman 2022-10-05 6:23 ` Greg Kroah-Hartman 2022-10-05 6:23 ` Greg Kroah-Hartman 2022-09-28 19:56 ` [PATCH v4 07/14] mailbox: Allow direct registration to a channel Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 08/14] virt: gunyah: msgq: Add hypercalls to send and receive messages Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 09/14] mailbox: Add Gunyah message queue mailbox Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-29 16:59 ` Bjorn Andersson 2022-09-29 16:59 ` Bjorn Andersson 2022-09-29 17:37 ` Jassi Brar 2022-09-29 17:37 ` Jassi Brar 2022-09-28 19:56 ` [PATCH v4 10/14] gunyah: sysfs: Add node to describe supported features Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-29 7:36 ` Joe Perches 2022-09-29 7:36 ` Joe Perches 2022-09-29 20:47 ` Elliot Berman 2022-09-29 20:47 ` Elliot Berman 2022-10-02 23:30 ` Jeff Johnson 2022-10-02 23:30 ` Jeff Johnson 2022-10-02 23:58 ` Joe Perches 2022-10-02 23:58 ` Joe Perches 2022-09-30 12:06 ` Greg Kroah-Hartman 2022-09-30 12:06 ` Greg Kroah-Hartman 2022-10-04 23:53 ` Elliot Berman 2022-10-04 23:53 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 11/14] gunyah: rsc_mgr: Add resource manager RPC core Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-28 19:56 ` [PATCH v4 12/14] gunyah: rsc_mgr: Add RPC for console services Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-30 12:22 ` Greg Kroah-Hartman 2022-09-30 12:22 ` Greg Kroah-Hartman 2022-10-03 1:46 ` new checkpatch flexible array test ? (was Re: [PATCH v4 12/14] gunyah: rsc_mgr: Add RPC for console services) Joe Perches 2022-10-03 1:46 ` Joe Perches 2022-10-03 5:29 ` Greg Kroah-Hartman 2022-10-03 5:29 ` Greg Kroah-Hartman 2022-10-03 5:38 ` Joe Perches 2022-10-03 5:38 ` Joe Perches 2022-10-31 18:23 ` Gustavo A. R. Silva 2022-10-31 18:23 ` Gustavo A. R. Silva 2022-09-28 19:56 ` [PATCH v4 13/14] gunyah: rsc_mgr: Add auxiliary devices for console Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-30 12:19 ` Greg Kroah-Hartman 2022-09-30 12:19 ` Greg Kroah-Hartman 2022-10-04 23:49 ` Elliot Berman 2022-10-04 23:49 ` Elliot Berman 2022-10-05 6:21 ` Greg Kroah-Hartman 2022-10-05 6:21 ` Greg Kroah-Hartman 2022-10-05 21:47 ` Elliot Berman 2022-10-05 21:47 ` Elliot Berman 2022-10-06 6:28 ` Greg Kroah-Hartman 2022-10-06 6:28 ` Greg Kroah-Hartman 2022-09-28 19:56 ` [PATCH v4 14/14] tty: gunyah: Add tty console driver for RM Console Services Elliot Berman 2022-09-28 19:56 ` Elliot Berman 2022-09-30 12:17 ` Greg Kroah-Hartman 2022-09-30 12:17 ` Greg Kroah-Hartman 2022-10-07 5:59 ` Elliot Berman 2022-10-07 5:59 ` Elliot Berman 2022-10-07 7:40 ` Greg Kroah-Hartman 2022-10-07 7:40 ` Greg Kroah-Hartman 2022-10-09 20:59 ` Elliot Berman 2022-10-09 20:59 ` Elliot Berman 2022-10-10 20:23 ` Greg Kroah-Hartman 2022-10-10 20:23 ` Greg Kroah-Hartman 2022-10-10 20:58 ` Elliot Berman 2022-10-10 20:58 ` Elliot Berman 2022-10-11 6:22 ` Greg Kroah-Hartman 2022-10-11 6:22 ` Greg Kroah-Hartman 2022-10-11 22:04 ` Elliot Berman 2022-10-11 22:04 ` Elliot Berman 2022-10-12 6:53 ` Greg Kroah-Hartman 2022-10-12 6:53 ` Greg Kroah-Hartman 2022-10-08 7:41 ` Zhou Furong 2022-10-08 7:41 ` Zhou Furong 2022-10-08 9:52 ` Greg Kroah-Hartman 2022-10-08 9:52 ` Greg Kroah-Hartman 2022-10-03 7:01 ` Jiri Slaby 2022-10-03 7:01 ` Jiri Slaby 2022-10-10 18:06 ` Elliot Berman 2022-10-10 18:06 ` Elliot Berman
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=Yzbcd0r768pRgRMr@kroah.com \ --to=gregkh@linuxfoundation.org \ --cc=agross@kernel.org \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=corbet@lwn.net \ --cc=devicetree@vger.kernel.org \ --cc=dmitry.baryshkov@linaro.org \ --cc=jassisinghbrar@gmail.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=mark.rutland@arm.com \ --cc=maz@kernel.org \ --cc=quic_bjorande@quicinc.com \ --cc=quic_cvanscha@quicinc.com \ --cc=quic_eberman@quicinc.com \ --cc=quic_mnalajal@quicinc.com \ --cc=quic_svaddagi@quicinc.com \ --cc=quic_tsoni@quicinc.com \ --cc=robh+dt@kernel.org \ --cc=sudeep.holla@arm.com \ --cc=will@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: linkBe 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.