Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3 intel-next] ice: add TTY for GNSS module for E810T device
Date: Mon, 13 Dec 2021 20:14:34 +0000	[thread overview]
Message-ID: <bce5f2e32aa835d43c9e2deba39df9342dfbaec7.camel@intel.com> (raw)
In-Reply-To: <20211213105234.397045-1-karol.kolacinski@intel.com>

On Mon, 2021-12-13 at 11:52 +0100, Karol Kolacinski wrote:
> Add a new ice_gnss.c file for holding the basic GNSS module
> functions.
> If the device supports GNSS module, call the new ice_gnss_init and
> ice_gnss_release functions where appropriate.
> 
> Implement basic functionality for reading the data from GNSS module
> using TTY device.
> 
> Add I2C read AQ command. It is now required for controlling the
> external
> physical connectors via external I2C port expander on E810-T
> adapters.
> 
> Future changes will introduce write functionality.
> 
> Signed-off-by: Karol Kolacinski <karol.kolacinski@intel.com>
> Signed-off-by: Sudhansu Sekhar Mishra <sudhansu.mishra@intel.com>
> ---
> V1 -> V2: Added CONFIG_TTY dependency
> V2 -> V3: Removed unnecessary & on pf->hw pointer check

<snip>

> +???????pf = gnss->back;
> +???????if (!pf || !pf->hw || !gnss->tty || !gnss->tty->port) {
> +???????????????err = -EFAULT;
> +???????????????goto exit;
> +???????}

../drivers/net/ethernet/intel/ice/ice_gnss.c: In function
ice_gnss_read:
../drivers/net/ethernet/intel/ice/ice_gnss.c:30:13: error: wrong type
argument to unary exclamation mark
  if (!pf || !pf->hw || !gnss->tty || !gnss->tty->port) {
             ^

I believe Piotr's comment meant the &pf->hw check is not needed at all.

  reply	other threads:[~2021-12-13 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 10:52 [Intel-wired-lan] [PATCH v3 intel-next] ice: add TTY for GNSS module for E810T device Karol Kolacinski
2021-12-13 20:14 ` Nguyen, Anthony L [this message]
2021-12-15 15:47   ` Piotr Raczynski

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=bce5f2e32aa835d43c9e2deba39df9342dfbaec7.camel@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@osuosl.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