From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>
Cc: Chunfeng Yun <chunfeng.yun@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Eddie Hung <eddie.hung@mediatek.com>,
stable@vger.kernel.org, Yuwen Ng <yuwen.ng@mediatek.com>
Subject: Re: [PATCH v2 3/4] usb: mtu3: fix list_head check warning
Date: Sun, 19 Dec 2021 11:40:51 +0100 [thread overview]
Message-ID: <Yb8MM2zL2Ecfzv1/@kroah.com> (raw)
In-Reply-To: <64b9453a-84c5-8d41-26d5-698d1ae9d473@gmail.com>
On Sun, Dec 19, 2021 at 01:14:25PM +0300, Sergei Shtylyov wrote:
> On 18.12.2021 12:57, Chunfeng Yun wrote:
>
> > This is caused by uninitialization of list_head.
>
> Again, there's no such word as "uninitialization" (even if it existed, it
> wouldn't mean what you wanted to say); please replace by "not initializing".
We are not English language scholars, most of us do not have English as
their native language. We all can understand what is being said here,
there's no need for any change, please do not be so critical.
thanks,
greg k-h
next prev parent reply other threads:[~2021-12-19 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 9:57 [PATCH v2 1/4] usb: mtu3: fix interval value for intr and isoc Chunfeng Yun
2021-12-18 9:57 ` [PATCH v2 2/4] usb: mtu3: add memory barrier before set GPD's HWO Chunfeng Yun
2021-12-18 9:57 ` [PATCH v2 3/4] usb: mtu3: fix list_head check warning Chunfeng Yun
2021-12-19 10:14 ` Sergei Shtylyov
2021-12-19 10:40 ` Greg Kroah-Hartman [this message]
2021-12-19 11:00 ` Sergei Shtylyov
2021-12-21 6:16 ` Chunfeng Yun
2021-12-18 9:57 ` [PATCH v2 4/4] usb: mtu3: set interval of FS intr and isoc endpoint Chunfeng Yun
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=Yb8MM2zL2Ecfzv1/@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chunfeng.yun@mediatek.com \
--cc=eddie.hung@mediatek.com \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=sergei.shtylyov@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yuwen.ng@mediatek.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