From: lizhe <sensor1010@163.com>
To: tiwai@suse.de
Cc: tiwai@suse.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH v5] serial: linflexuart: remove redundant uart type assignment
Date: Sun, 19 Mar 2023 18:55:48 +0800 (CST) [thread overview]
Message-ID: <e5498ef.1620.186f982de31.Coremail.sensor1010@163.com> (raw)
In-Reply-To: <ddcf396b-7b91-00f3-8c16-7de5dc891aef@kernel.org>
HI :
My name is Li zhe. i am chinese
At 2023-01-05 14:32:07, "Jiri Slaby" <jirislaby@kernel.org> wrote:
>On 04. 01. 23, 17:43, LIZHE wrote:
>> in linflex_config_port() the member variable type will be
>> assigned again. see linflex_connfig_port()
>
>Please use capitals when you start a sentence. And periods at the ends
>of them.
>
>> Signed-off-by: LIZHE <sensor1010@163.com>
>
>No, Lizhe was fine (or use your Chinese name. We support unicode so that
>would be fine too, as Greg stated).
>
>But you didn't include changelog to your previous v1-v4 patches; as
>stated by Ilpo.
>
>> Link: https://lore.kernel.org/all/20230103170948.3777-1-sensor1010@163.com/
>> ---
>> drivers/tty/serial/fsl_linflexuart.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/tty/serial/fsl_linflexuart.c b/drivers/tty/serial/fsl_linflexuart.c
>> index 6fc21b6684e6..34400cc6ac7f 100644
>> --- a/drivers/tty/serial/fsl_linflexuart.c
>> +++ b/drivers/tty/serial/fsl_linflexuart.c
>> @@ -837,7 +837,6 @@ static int linflex_probe(struct platform_device *pdev)
>> return PTR_ERR(sport->membase);
>>
>> sport->dev = &pdev->dev;
>> - sport->type = PORT_LINFLEXUART;
>> sport->iotype = UPIO_MEM;
>> sport->irq = platform_get_irq(pdev, 0);
>> sport->ops = &linflex_pops;
>
>--
>js
>suse labs
parent reply other threads:[~2023-03-20 19:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ddcf396b-7b91-00f3-8c16-7de5dc891aef@kernel.org>]
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=e5498ef.1620.186f982de31.Coremail.sensor1010@163.com \
--to=sensor1010@163.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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