From: Florian Eckert <fe@dev.tdt.de>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Eckert.Florian@googlemail.com, gregkh@linuxfoundation.org,
pavel@ucw.cz, lee@kernel.org, kabel@kernel.org,
u.kleine-koenig@pengutronix.de, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH 1/2] tty: add new helper function tty_get_mget
Date: Tue, 26 Sep 2023 14:03:59 +0200 [thread overview]
Message-ID: <2c36a83654942416cfdcb2e40ecb539d@dev.tdt.de> (raw)
In-Reply-To: <dc5ac2cb-71b3-4946-a58b-2ec353bc40a4@kernel.org>
Thanks for your fast respond!
>> @@ -2494,6 +2494,25 @@ static int send_break(struct tty_struct *tty,
>> unsigned int duration)
>> return retval;
>> }
>> +/**
>> + * tty_get_mget - get modem status
>
> Heh, the naming is funny. It apparently comes from tiocmget. But that
> comes from:
> tty ioctl modem get (TIOCMGET)
> tty ioctl modem set (TIOCMSET)
>
> So you should name it like tty_get_modem() not get_mget().
I didn't like the name too, but I couldn't think of another.
The function is returning the state of serial control and status
signals.
From your suggestion for the name, however, you can not deduce that at
all.
How would it be then with the following name?
tty_tioctl_state() ?
>
> Also those extra spaces around "-" caused some issues in the generated
> output and should be removed (everywhere).
Ok, I will change this in an own commit throughout the file.
Thanks
Florian
@jirislaby: Forgot to send this message to the mailing list as well!
next prev parent reply other threads:[~2023-09-26 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 9:36 [PATCH 0/2] ledtrig-tty: add new state evaluation Florian Eckert
2023-09-26 9:36 ` [PATCH 1/2] tty: add new helper function tty_get_mget Florian Eckert
2023-09-26 9:48 ` Jiri Slaby
2023-09-26 12:03 ` Florian Eckert [this message]
2023-09-26 9:36 ` [PATCH 2/2] trigger: ledtrig-tty: add new line mode to triggers Florian Eckert
2023-09-26 20:33 ` kernel test robot
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=2c36a83654942416cfdcb2e40ecb539d@dev.tdt.de \
--to=fe@dev.tdt.de \
--cc=Eckert.Florian@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kabel@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).