Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	<intel-wired-lan@lists.osuosl.org>,
	Michal Maloszewski <michal.maloszewski@intel.com>
Cc: Karol Kolacinski <karol.kolacinski@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v2] ice: use GNSS subsystem instead of TTY
Date: Wed, 21 Sep 2022 08:22:31 -0700	[thread overview]
Message-ID: <c814110c-4dae-462e-daea-de25ab29e176@intel.com> (raw)
In-Reply-To: <20220917004009.77412-1-arkadiusz.kubalewski@intel.com>



On 9/16/2022 5:40 PM, Arkadiusz Kubalewski wrote:
> 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<id>/device/
> 
> User expecting onboard GNSS receiver is now required to explicitly
> enable CONFIG_GNSS in kernel config.

I'm dropping this due to the lkp reported issues [1]. Please fix and 
resubmit.

Thanks,
Tony

> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>

[1] 
https://lore.kernel.org/intel-wired-lan/202209211139.VPM7En0j-lkp@intel.com/T/#u
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-09-21 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17  0:40 [Intel-wired-lan] [PATCH net-next v2] ice: use GNSS subsystem instead of TTY Arkadiusz Kubalewski
2022-09-21 15:22 ` Tony Nguyen [this message]
2022-09-23 11:31   ` Michalik, Michal

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=c814110c-4dae-462e-daea-de25ab29e176@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=karol.kolacinski@intel.com \
    --cc=michal.maloszewski@intel.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