[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X8YC1UGSfaarKMcV@localhost>
Date: Tue, 1 Dec 2020 09:46:13 +0100
From: Johan Hovold <johan@...nel.org>
To: Jiri Slaby <jirislaby@...nel.org>
Cc: Johan Hovold <johan@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Mychaela N . Falconia" <falcon@...ecalypso.org>,
linux-serial@...r.kernel.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] tty: add port flag to suppress ready signalling on
open
On Tue, Dec 01, 2020 at 06:49:07AM +0100, Jiri Slaby wrote:
> On 30. 11. 20, 16:37, Johan Hovold wrote:
> > --- a/include/linux/tty.h
> > +++ b/include/linux/tty.h
> > @@ -683,6 +684,19 @@ static inline void tty_port_set_kopened(struct tty_port *port, bool val)
> > clear_bit(TTY_PORT_KOPENED, &port->iflags);
> > }
> >
> > +static inline bool tty_port_nordy(struct tty_port *port)
>
> port can be const here.
Sure, but see below.
> > +{
> > + return test_bit(TTY_PORT_NORDY, &port->iflags);
> > +}
> > +
> > +static inline void tty_port_set_nordy(struct tty_port *port, bool val)
> > +{
> > + if (val)
> > + set_bit(TTY_PORT_NORDY, &port->iflags);
> > + else
> > + clear_bit(TTY_PORT_NORDY, &port->iflags);
>
> We have assign_bit() for these cases these days.
Right, but for both your comments this follows the pattern used by the
other port-flag helpers.
I can add a preparatory patch updating the current helpers, but I don't
think this needs to be a blocker.
Johan
Powered by blists - more mailing lists