From: Ira Weiny <ira.weiny@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Ira Weiny <ira.weiny@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>, Fan Ni <fan.ni@samsung.com>,
"Navneet Singh" <navneet.singh@intel.com>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
<linux-btrfs@vger.kernel.org>, <linux-cxl@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<nvdimm@lists.linux.dev>
Subject: Re: [PATCH v3 24/25] tools/testing/cxl: Make event logs dynamic
Date: Mon, 9 Sep 2024 08:57:42 -0500 [thread overview]
Message-ID: <66defed6b37c2_f937b29469@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20240827153204.00002bff@Huawei.com>
Jonathan Cameron wrote:
> On Fri, 16 Aug 2024 09:44:32 -0500
> Ira Weiny <ira.weiny@intel.com> wrote:
>
> > The test event logs were created as static arrays as an easy way to mock
> > events. Dynamic Capacity Device (DCD) test support requires events be
> > generated dynamically when extents are created or destroyed.
> >
> > Modify the event log storage to be dynamically allocated. Reuse the
> > static event data to create the dynamic events in the new logs without
> > inventing complex event injection for the previous tests. Simplify the
> > processing of the logs by using the event log array index as the handle.
> > Add a lock to manage concurrency required when user space is allowed to
> > control DCD extents
> >
> > Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> Probably make sense to spinkle some guard() magic in here
> to avoid all the places where you goto end of function to release the lock
Yes. Sorry this patch did not get as much self-review as it should have.
> >
> > ---
> > Changes:
> > [iweiny: rebase]
> > ---
> > tools/testing/cxl/test/mem.c | 278 ++++++++++++++++++++++++++-----------------
> > 1 file changed, 171 insertions(+), 107 deletions(-)
> >
> > diff --git a/tools/testing/cxl/test/mem.c b/tools/testing/cxl/test/mem.c
> > index 129f179b0ac5..674fc7f086cd 100644
> > --- a/tools/testing/cxl/test/mem.c
> > +++ b/tools/testing/cxl/test/mem.c
> > @@ -125,18 +125,27 @@ static struct {
> >
> > #define PASS_TRY_LIMIT 3
> >
> > -#define CXL_TEST_EVENT_CNT_MAX 15
> > +#define CXL_TEST_EVENT_CNT_MAX 17
>
> Seems you added a couple more. Don't do that in a patch
> just changing allocation approach.
>
> I could find 1 but not sure where other one came from!
I wasn't sure either. see below...
[snip]
> > @@ -233,8 +254,8 @@ static int mock_get_event(struct device *dev, struct cxl_mbox_cmd *cmd)
> > {
> > struct cxl_get_event_payload *pl;
> > struct mock_event_log *log;
> > - u16 nr_overflow;
> > u8 log_type;
> > + u16 handle;
> > int i;
> >
> > if (cmd->size_in != sizeof(log_type))
> > @@ -254,29 +275,39 @@ static int mock_get_event(struct device *dev, struct cxl_mbox_cmd *cmd)
> > memset(cmd->payload_out, 0, struct_size(pl, records, 0));
> >
> > log = event_find_log(dev, log_type);
> > - if (!log || event_log_empty(log))
> > + if (!log)
> > return 0;
> >
> > pl = cmd->payload_out;
> >
> > - for (i = 0; i < ret_limit && !event_log_empty(log); i++) {
> > - memcpy(&pl->records[i], event_get_current(log),
> > - sizeof(pl->records[i]));
> > - pl->records[i].event.generic.hdr.handle =
> > - event_get_cur_event_handle(log);
> > - log->cur_idx++;
> > + read_lock(&log->lock);
> > +
> > + handle = log->cur_handle;
> > + dev_dbg(dev, "Get log %d handle %u next %u\n",
> > + log_type, handle, log->next_handle);
> > + for (i = 0;
> > + i < ret_limit && handle != log->next_handle;
> As below, maybe combine 2 lines above into 1.
Ok. done.
>
>
> > + i++, event_inc_handle(&handle)) {
> > + struct cxl_event_record_raw *cur;
> > +
> > + cur = log->events[handle];
> > + dev_dbg(dev, "Sending event log %d handle %d idx %u\n",
> > + log_type, le16_to_cpu(cur->event.generic.hdr.handle),
> > + handle);
> > + memcpy(&pl->records[i], cur, sizeof(pl->records[i]));
> > + pl->records[i].event.generic.hdr.handle = cpu_to_le16(handle);
> > }
> >
> > cmd->size_out = struct_size(pl, records, i);
> > pl->record_count = cpu_to_le16(i);
> > - if (!event_log_empty(log))
> > + if (log->nr_events > i)
> > pl->flags |= CXL_GET_EVENT_FLAG_MORE_RECORDS;
> >
> > if (log->nr_overflow) {
> > u64 ns;
> >
> > pl->flags |= CXL_GET_EVENT_FLAG_OVERFLOW;
> > - pl->overflow_err_count = cpu_to_le16(nr_overflow);
> > + pl->overflow_err_count = cpu_to_le16(log->nr_overflow);
> > ns = ktime_get_real_ns();
> > ns -= 5000000000; /* 5s ago */
> > pl->first_overflow_timestamp = cpu_to_le64(ns);
> > @@ -285,16 +316,17 @@ static int mock_get_event(struct device *dev, struct cxl_mbox_cmd *cmd)
> > pl->last_overflow_timestamp = cpu_to_le64(ns);
> > }
> >
> > + read_unlock(&log->lock);
> Another one maybe for guard()
done.
>
> > return 0;
> > }
> >
> > static int mock_clear_event(struct device *dev, struct cxl_mbox_cmd *cmd)
> > {
> > struct cxl_mbox_clear_event_payload *pl = cmd->payload_in;
> > - struct mock_event_log *log;
> > u8 log_type = pl->event_log;
> > + struct mock_event_log *log;
> > + int nr, rc = 0;
> > u16 handle;
> > - int nr;
> >
> > if (log_type >= CXL_EVENT_TYPE_MAX)
> > return -EINVAL;
> > @@ -303,24 +335,23 @@ static int mock_clear_event(struct device *dev, struct cxl_mbox_cmd *cmd)
> > if (!log)
> > return 0; /* No mock data in this log */
> >
> > - /*
> > - * This check is technically not invalid per the specification AFAICS.
> > - * (The host could 'guess' handles and clear them in order).
> > - * However, this is not good behavior for the host so test it.
> > - */
> > - if (log->clear_idx + pl->nr_recs > log->cur_idx) {
> > - dev_err(dev,
> > - "Attempting to clear more events than returned!\n");
> > - return -EINVAL;
> > - }
> > + write_lock(&log->lock);
> Use a guard()?
done.
> >
> > /* Check handle order prior to clearing events */
> > - for (nr = 0, handle = event_get_clear_handle(log);
> > - nr < pl->nr_recs;
> > - nr++, handle++) {
> > + handle = log->cur_handle;
> > + for (nr = 0;
> > + nr < pl->nr_recs && handle != log->next_handle;
>
> I'd combine the two lines above.
Ok. done.
>
> > + nr++, event_inc_handle(&handle)) {
> > +
> > + dev_dbg(dev, "Checking clear of %d handle %u plhandle %u\n",
> > + log_type, handle,
> > + le16_to_cpu(pl->handles[nr]));
> > +
> > if (handle != le16_to_cpu(pl->handles[nr])) {
> > - dev_err(dev, "Clearing events out of order\n");
> > - return -EINVAL;
> > + dev_err(dev, "Clearing events out of order %u %u\n",
> > + handle, le16_to_cpu(pl->handles[nr]));
> > + rc = -EINVAL;
> > + goto unlock;
> > }
> > }
> >
> > @@ -328,25 +359,12 @@ static int mock_clear_event(struct device *dev, struct cxl_mbox_cmd *cmd)
> > log->nr_overflow = 0;
> >
> > /* Clear events */
> > - log->clear_idx += pl->nr_recs;
> > - return 0;
> > -}
>
> >
> > struct cxl_event_record_raw maint_needed = {
> > @@ -475,8 +493,27 @@ static int mock_set_timestamp(struct cxl_dev_state *cxlds,
> > return 0;
> > }
> >
>
> > +static void cxl_mock_add_event_logs(struct cxl_mockmem_data *mdata)
> > {
> > + struct mock_event_store *mes = &mdata->mes;
> > + struct device *dev = mdata->mds->cxlds.dev;
> > +
> > put_unaligned_le16(CXL_GMER_VALID_CHANNEL | CXL_GMER_VALID_RANK,
> > &gen_media.rec.media_hdr.validity_flags);
> >
> > @@ -484,43 +521,60 @@ static void cxl_mock_add_event_logs(struct mock_event_store *mes)
> > CXL_DER_VALID_BANK | CXL_DER_VALID_COLUMN,
> > &dram.rec.media_hdr.validity_flags);
> >
> > - mes_add_event(mes, CXL_EVENT_TYPE_INFO, &maint_needed);
> > - mes_add_event(mes, CXL_EVENT_TYPE_INFO,
> > + dev_dbg(dev, "Generating fake event logs %d\n",
> > + CXL_EVENT_TYPE_INFO);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_INFO, &maint_needed);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_INFO,
> > (struct cxl_event_record_raw *)&gen_media);
> > - mes_add_event(mes, CXL_EVENT_TYPE_INFO,
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_INFO,
> > (struct cxl_event_record_raw *)&mem_module);
> > mes->ev_status |= CXLDEV_EVENT_STATUS_INFO;
> >
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &maint_needed);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL,
> > + dev_dbg(dev, "Generating fake event logs %d\n",
> > + CXL_EVENT_TYPE_FAIL);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &maint_needed);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL,
> > + (struct cxl_event_record_raw *)&mem_module);
>
> So this one is new? I can't spot the other one...
Its coming back to me now. The cxl-events.sh test relied on an expected number
of each type of event (Including an overflow count) which were completely
fabricated previous to this patch.
num_overflow_expected=1
num_fatal_expected=2
num_failure_expected=16
num_info_expected=3
To maintain backwards compatibility this new code needed to preserve those
counts. The buffers and number of entries were adjusted to make the output
match. However now the logs need to actually over flow to create the overflow
error. Furthermore, the handles are the array entries. cxl-events.sh passes
before and after this patch.
That said, my math was wrong. A max of 16 with 16+ entries added to the
failure log should result in the counts above. I added a couple extra to the
overflow though.
Good catch on this. I basically hacked it to match and moved on. I've cleaned
it up for the next version.
>
>
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL,
> > (struct cxl_event_record_raw *)&dram);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL,
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL,
> > (struct cxl_event_record_raw *)&gen_media);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL,
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL,
> > (struct cxl_event_record_raw *)&mem_module);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL,
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL,
> > (struct cxl_event_record_raw *)&dram);
> > /* Overflow this log */
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FAIL, &hardware_replace);
> > mes->ev_status |= CXLDEV_EVENT_STATUS_FAIL;
> >
> > - mes_add_event(mes, CXL_EVENT_TYPE_FATAL, &hardware_replace);
> > - mes_add_event(mes, CXL_EVENT_TYPE_FATAL,
> > + dev_dbg(dev, "Generating fake event logs %d\n",
> > + CXL_EVENT_TYPE_FATAL);
> The dev_dbg() fine but not really part of making it dynamic, so adds
> a bit of noise. Maybe not worth splitting out though.
It's just debugging that we are indeed adding these to the now dynamic list. I
added a print for each type. I've added even more debugging with the clean up.
I'm going to leave it in for now because it is part of ensuring the dynamic
events work.
Thanks,
Ira
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FATAL, &hardware_replace);
> > + add_event_from_static(mdata, CXL_EVENT_TYPE_FATAL,
> > (struct cxl_event_record_raw *)&dram);
> > mes->ev_status |= CXLDEV_EVENT_STATUS_FATAL;
> > }
>
>
next prev parent reply other threads:[~2024-09-09 13:57 UTC|newest]
Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 14:44 [PATCH v3 00/25] DCD: Add support for Dynamic Capacity Devices (DCD) Ira Weiny
2024-08-16 14:44 ` [PATCH v3 01/25] range: Add range_overlaps() Ira Weiny
2024-08-16 14:44 ` [PATCH v3 02/25] printk: Add print format (%par) for struct range Ira Weiny
2024-08-20 14:08 ` Petr Mladek
2024-08-22 17:53 ` Ira Weiny
2024-08-22 18:10 ` Andy Shevchenko
2024-08-26 13:23 ` Petr Mladek
2024-08-26 17:23 ` Andy Shevchenko
2024-08-26 21:17 ` Ira Weiny
2024-08-27 7:43 ` Petr Mladek
2024-08-27 13:21 ` Andy Shevchenko
2024-08-27 21:44 ` Ira Weiny
2024-08-27 13:17 ` Andy Shevchenko
2024-08-28 4:12 ` Ira Weiny
2024-08-28 13:50 ` Andy Shevchenko
2024-08-26 13:17 ` Petr Mladek
2024-08-26 13:24 ` Andy Shevchenko
2024-08-16 14:44 ` [PATCH v3 03/25] dax: Document dax dev range tuple Ira Weiny
2024-08-16 20:58 ` Dave Jiang
2024-08-23 15:29 ` Jonathan Cameron
2024-08-16 14:44 ` [PATCH v3 04/25] cxl/pci: Delay event buffer allocation Ira Weiny
2024-09-03 6:49 ` Li, Ming4
2024-09-05 19:44 ` Fan Ni
2024-08-16 14:44 ` [PATCH v3 05/25] cxl/mbox: Flag support for Dynamic Capacity Devices (DCD) ira.weiny
2024-09-03 6:50 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 06/25] cxl/mem: Read dynamic capacity configuration from the device ira.weiny
2024-08-16 21:45 ` Dave Jiang
2024-08-20 17:01 ` Fan Ni
2024-08-23 2:01 ` Ira Weiny
2024-08-23 2:02 ` Ira Weiny
2024-08-23 15:45 ` Jonathan Cameron
2024-08-16 14:44 ` [PATCH v3 07/25] cxl/core: Separate region mode from decoder mode ira.weiny
2024-08-16 22:11 ` Dave Jiang
2024-08-23 15:47 ` Jonathan Cameron
2024-09-03 6:56 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 08/25] cxl/region: Add dynamic capacity decoder and region modes ira.weiny
2024-08-16 22:14 ` Dave Jiang
2024-09-03 6:57 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 09/25] cxl/hdm: Add dynamic capacity size support to endpoint decoders ira.weiny
2024-08-16 23:08 ` Dave Jiang
2024-08-23 2:26 ` Ira Weiny
2024-08-23 16:09 ` Jonathan Cameron
2024-08-16 14:44 ` [PATCH v3 10/25] cxl/port: Add endpoint decoder DC mode support to sysfs ira.weiny
2024-08-16 23:17 ` Dave Jiang
2024-08-23 16:12 ` Jonathan Cameron
2024-08-16 14:44 ` [PATCH v3 11/25] cxl/mem: Expose DCD partition capabilities in sysfs ira.weiny
2024-08-16 23:42 ` Dave Jiang
2024-08-23 2:28 ` Ira Weiny
2024-08-23 14:58 ` Dave Jiang
2024-08-23 16:14 ` Jonathan Cameron
2024-08-16 14:44 ` [PATCH v3 12/25] cxl/region: Refactor common create region code Ira Weiny
2024-08-16 23:43 ` Dave Jiang
2024-08-22 18:51 ` Fan Ni
2024-08-23 16:17 ` Jonathan Cameron
2024-09-03 7:04 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 13/25] cxl/region: Add sparse DAX region support ira.weiny
2024-08-16 23:51 ` Dave Jiang
2024-08-22 18:50 ` Fan Ni
2024-08-23 16:59 ` Jonathan Cameron
2024-09-03 2:15 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 14/25] cxl/events: Split event msgnum configuration from irq setup Ira Weiny
2024-08-16 23:57 ` Dave Jiang
2024-08-22 21:39 ` Fan Ni
2024-08-23 17:01 ` Jonathan Cameron
2024-09-03 7:06 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 15/25] cxl/pci: Factor out interrupt policy check Ira Weiny
2024-08-22 21:41 ` Fan Ni
2024-09-03 7:07 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 16/25] cxl/mem: Configure dynamic capacity interrupts ira.weiny
2024-08-17 0:02 ` Dave Jiang
2024-08-23 17:08 ` Jonathan Cameron
2024-09-03 7:09 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 17/25] cxl/core: Return endpoint decoder information from region search Ira Weiny
2024-08-19 16:35 ` Dave Jiang
2024-08-23 17:12 ` Jonathan Cameron
2024-09-03 7:10 ` Li, Ming4
2024-08-16 14:44 ` [PATCH v3 18/25] cxl/extent: Process DCD events and realize region extents ira.weiny
2024-08-19 18:51 ` Dave Jiang
2024-08-23 2:53 ` Ira Weiny
2024-08-23 21:32 ` Fan Ni
2024-08-27 12:08 ` Jonathan Cameron
2024-08-27 16:02 ` Fan Ni
2024-08-27 13:18 ` Jonathan Cameron
2024-08-29 21:16 ` Ira Weiny
2024-08-30 9:21 ` Jonathan Cameron
2024-09-03 6:37 ` Li, Ming4
2024-09-05 19:30 ` Fan Ni
2024-08-16 14:44 ` [PATCH v3 19/25] cxl/region/extent: Expose region extent information in sysfs ira.weiny
2024-08-19 19:05 ` Dave Jiang
2024-08-23 2:58 ` Ira Weiny
2024-08-23 17:17 ` Jonathan Cameron
2024-08-23 17:19 ` Jonathan Cameron
2024-08-28 17:44 ` Fan Ni
2024-08-16 14:44 ` [PATCH v3 20/25] dax/bus: Factor out dev dax resize logic Ira Weiny
2024-08-19 22:35 ` Dave Jiang
2024-08-27 13:26 ` Jonathan Cameron
2024-08-29 21:36 ` Ira Weiny
2024-08-16 14:44 ` [PATCH v3 21/25] dax/region: Create resources on sparse DAX regions ira.weiny
2024-08-18 11:38 ` Markus Elfring
2024-08-19 23:30 ` Dave Jiang
2024-08-23 14:28 ` Ira Weiny
2024-08-27 14:12 ` Jonathan Cameron
2024-08-29 21:54 ` Ira Weiny
2024-08-16 14:44 ` [PATCH v3 22/25] cxl/region: Read existing extents on region creation ira.weiny
2024-08-20 0:06 ` Dave Jiang
2024-08-23 21:31 ` Ira Weiny
2024-08-27 14:19 ` Jonathan Cameron
2024-09-05 19:35 ` Fan Ni
2024-08-16 14:44 ` [PATCH v3 23/25] cxl/mem: Trace Dynamic capacity Event Record ira.weiny
2024-08-20 22:54 ` Dave Jiang
2024-08-26 18:02 ` Ira Weiny
2024-08-27 14:20 ` Jonathan Cameron
2024-09-05 19:38 ` Fan Ni
2024-08-16 14:44 ` [PATCH v3 24/25] tools/testing/cxl: Make event logs dynamic Ira Weiny
2024-08-20 23:30 ` Dave Jiang
2024-08-27 14:32 ` Jonathan Cameron
2024-09-09 13:57 ` Ira Weiny [this message]
2024-08-16 14:44 ` [PATCH v3 25/25] tools/testing/cxl: Add DC Regions to mock mem data Ira Weiny
2024-08-27 14:39 ` Jonathan Cameron
2024-09-09 14:08 ` Ira Weiny
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=66defed6b37c2_f937b29469@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=clm@fb.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=dsterba@suse.com \
--cc=fan.ni@samsung.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=navneet.singh@intel.com \
--cc=nvdimm@lists.linux.dev \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=vishal.l.verma@intel.com \
/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