From: Greg KH <gregkh@linuxfoundation.org>
To: cael <juanfengpy@gmail.com>
Cc: jirislaby@kernel.org, ilpo.jarvinen@linux.intel.com,
benbjiang@tencent.com, robinlai@tencent.com,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v5] tty: fix hang on tty device with no_room set
Date: Mon, 27 Jun 2022 14:05:36 +0200 [thread overview]
Message-ID: <YrmdEJrM3z6Dbvgn@kroah.com> (raw)
In-Reply-To: <1655291821-19676-1-git-send-email-juanfengpy@gmail.com>
On Wed, Jun 15, 2022 at 07:17:01PM +0800, cael wrote:
> From: caelli <juanfengpy@gmail.com>
Can you please use the name you use to sign legal documents as the
number of different names being used and written here is totally
confusing. Please use your native language if that's an issue, that
would be best.
Also, why not use your corporate email address as the From: and
signed-off-by line also? That is preferred, and in this case, I'm going
to ask for it given the confusion that has happened so far in this
thread in the past.
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-27 12:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 2:21 tty: fix a possible hang on tty device cael
2022-05-24 9:11 ` Ilpo Järvinen
2022-05-24 11:09 ` cael
2022-05-24 11:40 ` Ilpo Järvinen
2022-05-24 12:47 ` cael
2022-05-24 13:25 ` Ilpo Järvinen
2022-05-25 10:36 ` cael
2022-05-25 11:21 ` Ilpo Järvinen
2022-05-30 13:13 ` cael
2022-05-31 12:37 ` Ilpo Järvinen
2022-06-01 9:38 ` Greg KH
2022-06-01 13:39 ` cael
2022-06-01 14:47 ` Greg KH
2022-06-01 15:28 ` Ilpo Järvinen
2022-06-06 13:40 ` cael
2022-06-06 14:43 ` Greg KH
2022-06-11 6:50 ` cael
2022-06-11 7:32 ` Greg KH
2022-06-13 12:30 ` [PATCH v3] tty: fix hang on tty device with no_room set juanfengpy
2022-06-13 17:20 ` Greg KH
2022-06-15 3:45 ` [PATCH v4] " cael
2022-06-15 5:00 ` Greg KH
2022-06-15 7:57 ` Ilpo Järvinen
2022-06-15 9:29 ` Greg KH
2022-06-15 11:17 ` [PATCH v5] " cael
2022-06-15 11:29 ` Ilpo Järvinen
2022-06-15 13:33 ` caelli
2022-06-27 12:05 ` Greg KH [this message]
2022-06-27 13:53 ` [PATCH v6] " juanfengpy
2023-03-17 2:41 ` [PATCH v7] " juanfengpy
2023-03-17 6:32 ` Jiri Slaby
2023-03-17 7:25 ` [PATCH v8] " juanfengpy
2023-04-06 2:44 ` [PATCH v9] " juanfengpy
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=YrmdEJrM3z6Dbvgn@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benbjiang@tencent.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=juanfengpy@gmail.com \
--cc=linux-serial@vger.kernel.org \
--cc=robinlai@tencent.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;
as well as URLs for NNTP newsgroup(s).