From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: Jiri Slaby <jslaby@suse.com>,
linux-kernel@vger.kernel.org,
Fabien Dessenne <fabien.dessenne@st.com>
Subject: Re: [PATCH] Revert "tty: fix NULL pointer issue when tty_port ops is not set"
Date: Wed, 3 Apr 2019 10:06:49 +0200 [thread overview]
Message-ID: <20190403080649.GA12019@kroah.com> (raw)
In-Reply-To: <20190403074053.5961-1-johan@kernel.org>
On Wed, Apr 03, 2019 at 09:40:53AM +0200, Johan Hovold wrote:
> This reverts commit f4e68d58cf2b20a581759bbc7228052534652673.
>
> TTY drivers using the tty-port abstraction all provide a pointer to a
> set of port operations, which specifically cannot be NULL (or we'd find
> out at first attempt to open a port).
>
> Revert the recent commit which added unnecessary NULL-checks and whose
> commit message indicated that it was fixing a real problem, which it did
> not.
>
> Note that even the two tty drivers for virtual devices currently
> providing an empty set of operations probably should be implementing at
> least some of the callbacks.
This was a "future fix" for a driver that is under review for 5.2, see
the email thread:
Subject: [PATCH 0/2] TTY: add rpmsg tty driver
It didn't want/need the port pointer, if that is incorrect, that's fine,
I'll gladly revert this, but as-is this patch isn't hurting anything,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2019-04-03 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 7:40 [PATCH] Revert "tty: fix NULL pointer issue when tty_port ops is not set" Johan Hovold
2019-04-03 8:06 ` Greg Kroah-Hartman [this message]
2019-04-03 8:26 ` Johan Hovold
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=20190403080649.GA12019@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fabien.dessenne@st.com \
--cc=johan@kernel.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
/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