From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Max Staudt <max@enpas.org>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] net: nfc: remove casts from tty->disc_data
Date: Thu, 3 Aug 2023 08:51:06 +0200 [thread overview]
Message-ID: <2023080359-senate-expose-46b2@gregkh> (raw)
In-Reply-To: <6808de4a-6002-e8bc-5921-06b5938dc69e@kernel.org>
On Thu, Aug 03, 2023 at 07:08:07AM +0200, Jiri Slaby wrote:
> On 02. 08. 23, 21:07, Jakub Kicinski wrote:
> > On Tue, 1 Aug 2023 08:22:37 +0200 Jiri Slaby (SUSE) wrote:
> > > tty->disc_data is 'void *', so there is no need to cast from that.
> > > Therefore remove the casts and assign the pointer directly.
> >
> > Which tree are these expected to flow thru?
>
> The intention was through the tty tree. But I don't mind either way -- it's
> up to you Greg.
I'll take them, thanks!
greg k-h
prev parent reply other threads:[~2023-08-03 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 6:22 [PATCH 0/2] tty: remove casts from tty->disc_data Jiri Slaby (SUSE)
2023-08-01 6:22 ` [PATCH 1/2] can: can327: " Jiri Slaby (SUSE)
2023-08-01 12:25 ` Simon Horman
2023-08-01 13:46 ` Max Staudt
2023-08-01 6:22 ` [PATCH 2/2] net: nfc: " Jiri Slaby (SUSE)
2023-08-01 12:26 ` Simon Horman
2023-08-01 13:46 ` Max Staudt
2023-08-02 19:07 ` Jakub Kicinski
2023-08-03 5:08 ` Jiri Slaby
2023-08-03 6:51 ` Greg KH [this message]
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=2023080359-senate-expose-46b2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jirislaby@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=max@enpas.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wg@grandegger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.