From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, arkadiusz.kubalewski@intel.com,
netdev@vger.kernel.org, johan@kernel.org,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
alexandr.lobakin@intel.com, karol.kolacinski@intel.com,
michal.michalik@intel.com, gurucharanx.g@intel.com
Subject: Re: [PATCH net-next v2 1/1] ice: use GNSS subsystem instead of TTY
Date: Fri, 20 Jan 2023 13:30:16 +0000 [thread overview]
Message-ID: <167422141694.18652.7138102508736773253.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230119005836.2068818-1-anthony.l.nguyen@intel.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 18 Jan 2023 16:58:36 -0800 you wrote:
> From: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
>
> Previously support for GNSS was implemented as a TTY driver, it allowed
> to access GNSS receiver on /dev/ttyGNSS_<bus><func>.
>
> Use generic GNSS subsystem API instead of implementing own TTY driver.
> The receiver is accessible on /dev/gnss<id>. In case of multiple receivers
> in the OS, correct device can be found by enumerating either:
> - /sys/class/net/<eth port>/device/gnss/
> - /sys/class/gnss/gnss<id>/device/
>
> [...]
Here is the summary with links:
- [net-next,v2,1/1] ice: use GNSS subsystem instead of TTY
https://git.kernel.org/netdev/net-next/c/c7ef8221ca7d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-01-20 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 0:58 [PATCH net-next v2 1/1] ice: use GNSS subsystem instead of TTY Tony Nguyen
2023-01-19 13:47 ` Greg KH
2023-01-20 13:30 ` patchwork-bot+netdevbpf [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=167422141694.18652.7138102508736773253.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandr.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=gurucharanx.g@intel.com \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=karol.kolacinski@intel.com \
--cc=kuba@kernel.org \
--cc=michal.michalik@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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).