From: Dan Williams <dan.j.williams@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>,
Nabeel M Mohamed <nabeelmd.linux@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
<linux-cxl@vger.kernel.org>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
"Dan Williams" <dan.j.williams@intel.com>, <linuxarm@huawei.com>
Subject: Re: [PATCH v2] cxl/pci: Set the device timestamp
Date: Fri, 21 Apr 2023 18:34:31 -0700 [thread overview]
Message-ID: <644339a7175c0_1b662941c@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20230223164227.djns4grt3qeydmn6@offworld>
Davidlohr Bueso wrote:
> On Wed, 22 Feb 2023, Nabeel M Mohamed wrote:
>
> >So, I'm wondering if there's any checklist listing the prerequisites
> >for submitting a patch to the CXL driver - for instance, requirements
> >on adding new tests for coverage, any existing CXL regression suites
> >that the patch must pass, etc.
>
> Btw we might want to support timestamps in the mock device, no? I am
> aware that qemu has both get and set.
>
> --<8-----
> [PATCH] cxl/test: Add mock test for set_timestamp
Mind resending this in its own thread? b4 can't grab this as it's a
reply to another patch, and the above is not a valid scissors line. I
tried manually fixing that up, but git am is still not happy:
$ git am -c patch -s
warning: Patch sent with format=flowed; space at the end of lines might be lost.
Applying: cxl/test: Add mock test for set_timestamp
error: corrupt patch at line 16
Patch failed at 0001 cxl/test: Add mock test for set_timestamp
prev parent reply other threads:[~2023-04-22 1:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:13 [PATCH v2] cxl/pci: Set the device timestamp Jonathan Cameron
2023-01-30 19:29 ` Dan Williams
2023-02-22 15:34 ` Nabeel M Mohamed
2023-02-22 16:27 ` Jonathan Cameron
2023-02-23 3:55 ` Nabeel M Mohamed
2023-02-23 15:05 ` Jonathan Cameron
2023-02-23 16:10 ` Nabeel M Mohamed
2023-02-23 16:42 ` Davidlohr Bueso
2023-02-23 22:11 ` Ira Weiny
2023-04-22 1:34 ` Dan Williams [this message]
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=644339a7175c0_1b662941c@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=nabeelmd.linux@gmail.com \
--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