From: Jakub Kicinski <kuba@kernel.org>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Jonathan Lemon <jonathan.lemon@gmail.com>,
Richard Cochran <richardcochran@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net] ptp: ocp: adjust serial port symlink creation
Date: Thu, 9 May 2024 20:23:49 -0700 [thread overview]
Message-ID: <20240509202349.5cc20dd8@kernel.org> (raw)
In-Reply-To: <20240508132144.11560-1-vadim.fedorenko@linux.dev>
On Wed, 8 May 2024 13:21:44 +0000 Vadim Fedorenko wrote:
> +#include "../tty/serial/8250/8250.h"
Hm, is there no cleaner way to get the device structs?
Could you repost and CC the serial/8250 maintainers?
Greg can probably tell us how to do this..
--
pw-bot: cr
prev parent reply other threads:[~2024-05-10 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 13:21 [PATCH net] ptp: ocp: adjust serial port symlink creation Vadim Fedorenko
2024-05-10 3:23 ` Jakub Kicinski [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=20240509202349.5cc20dd8@kernel.org \
--to=kuba@kernel.org \
--cc=jonathan.lemon@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).