From: Zhou Wang <wangzhou1@hisilicon.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kai Ye <yekai13@huawei.com>,
<linux-accelerators@lists.ozlabs.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<zhangfei.gao@linaro.org>
Subject: Re: [PATCH v3 0/2] uacce: fix some coding styles
Date: Mon, 2 Nov 2020 15:38:49 +0800 [thread overview]
Message-ID: <5F9FB789.9090204@hisilicon.com> (raw)
In-Reply-To: <20201102070937.GA71996@kroah.com>
On 2020/11/2 15:09, Greg Kroah-Hartman wrote:
> On Mon, Nov 02, 2020 at 02:41:12PM +0800, Zhou Wang wrote:
>> On 2020/9/23 18:09, Kai Ye wrote:
>>> 1. delete some redundant code.
>>> 2. modify the module author information. "Hisilicon"
>>> spelling is error.
>>>
>>> Changes v2 -> v3:
>>> Two things, splited to two patches.
>>> Changes v1 -> v2:
>>> deleted extra NULL pointer check in uacce_fops.
>>>
>>> Kai Ye (2):
>>> uacce: fix some coding styles
>>> uacce: modify the module author information.
>>>
>>> drivers/misc/uacce/uacce.c | 13 +------------
>>> 1 file changed, 1 insertion(+), 12 deletions(-)
>>>
>>
>> Hi Hartman，
>>
>> Could you help to take this clean up patch?
>
> I do not see a patch here :(
I know the reason, Kai Ye did not To you and I also added your
Email address in this ping :) I have replied patches directly.
Could you take them?
Best,
Zhou
>
> If I have missed something, please resend it.
>
> thanks,
>
> greg k-h
> .
>
next prev parent reply other threads:[~2020-11-02 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 10:09 [PATCH v3 0/2] uacce: fix some coding styles Kai Ye
2020-09-23 10:09 ` [PATCH v3 1/2] uacce: delete some redundant code Kai Ye
2020-11-02 7:37 ` Zhou Wang
2020-09-23 10:09 ` [PATCH v3 2/2] uacce: modify the module author information Kai Ye
2020-11-02 7:38 ` Zhou Wang
2020-10-19 7:02 ` [PATCH v3 0/2] uacce: fix some coding styles yekai(A)
2020-11-02 6:41 ` Zhou Wang
2020-11-02 7:09 ` Greg Kroah-Hartman
2020-11-02 7:38 ` Zhou Wang [this message]
2020-11-02 8:33 ` Greg Kroah-Hartman
2020-11-02 8:39 ` Zhou Wang
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=5F9FB789.9090204@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-accelerators@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=yekai13@huawei.com \
--cc=zhangfei.gao@linaro.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