From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jeongtae Park <jtp.park@samsung.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>, Fan Ni <fan.ni@samsung.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Kyungsan Kim <ks0204.kim@samsung.com>,
Wonjae Lee <wj28.lee@samsung.com>,
Hojin Nam <hj96.nam@samsung.com>,
Junhyeok Im <junhyeok.im@samsung.com>,
Jehoon Park <jehoon.park@samsung.com>,
Jeongtae Park <jeongtae.park@gmail.com>
Subject: Re: [PATCH v2 0/7] cxl: Fix checkpatch issues
Date: Thu, 5 Oct 2023 10:08:42 +0200 [thread overview]
Message-ID: <2023100506-arena-sip-e5da@gregkh> (raw)
In-Reply-To: <20230922113443.3297726-1-jtp.park@samsung.com>
On Fri, Sep 22, 2023 at 08:34:43PM +0900, Jeongtae Park wrote:
> Changes since v1: [1]
> - Seperate a fix for whitespace error/warnings in memdev (Dave)
> - Drop a fix for a traceevent macro (Dave)
> - Add reviewed-by tags
>
> [1]: https://lore.kernel.org/lkml/20230921025110.3717583-1-jtp.park@samsung.com/
>
> ---
> Cover letter same as v1
None of these emails were properly threaded (look at lore.kernel.org for
proof.)
Please fix your email client to do this properly, your v1 of this series
was threaded correctly, so something changed here :(
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-05 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230922113157epcas2p212c253d8fe4f6935ee5cbe284254cc68@epcas2p2.samsung.com>
2023-09-22 11:34 ` [PATCH v2 0/7] cxl: Fix checkpatch issues Jeongtae Park
2023-10-05 8:08 ` Greg Kroah-Hartman [this message]
2023-10-05 8:42 ` Jeongtae Park
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=2023100506-arena-sip-e5da@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=hj96.nam@samsung.com \
--cc=jehoon.park@samsung.com \
--cc=jeongtae.park@gmail.com \
--cc=jonathan.cameron@huawei.com \
--cc=jtp.park@samsung.com \
--cc=junhyeok.im@samsung.com \
--cc=ks0204.kim@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=wj28.lee@samsung.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