netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: Richard Cochran <richardcochran@gmail.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"Machnikowski, Maciej" <maciej.machnikowski@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH net-next 2/5] ice: add support for auxiliary input/output pins
Date: Mon, 28 Jun 2021 22:45:50 +0000	[thread overview]
Message-ID: <fcc626d6773745ae9ecee10dfaca1316@intel.com> (raw)
In-Reply-To: <20210626140245.GA15724@hoboy.vegasvil.org>



> -----Original Message-----
> From: Richard Cochran <richardcochran@gmail.com>
> Sent: Saturday, June 26, 2021 7:03 AM
> To: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
> Cc: davem@davemloft.net; kuba@kernel.org; Machnikowski, Maciej
> <maciej.machnikowski@intel.com>; netdev@vger.kernel.org; Keller, Jacob E
> <jacob.e.keller@intel.com>
> Subject: Re: [PATCH net-next 2/5] ice: add support for auxiliary input/output pins
> 
> On Fri, Jun 25, 2021 at 11:57:30AM -0700, Tony Nguyen wrote:
> 
> > @@ -783,6 +1064,17 @@ static long ice_ptp_create_clock(struct ice_pf *pf)
> >  	info = &pf->ptp.info;
> >  	dev = ice_pf_to_dev(pf);
> >
> > +	/* Allocate memory for kernel pins interface */
> > +	if (info->n_pins) {
> > +		info->pin_config = devm_kcalloc(dev, info->n_pins,
> > +						sizeof(*info->pin_config),
> > +						GFP_KERNEL);
> > +		if (!info->pin_config) {
> > +			info->n_pins = 0;
> > +			return -ENOMEM;
> > +		}
> > +	}
> 
> How is this supposed to worK?
> 
> - If n_pins is non-zero, there must also be a ptp_caps.verify method,
>   but you don't provide one.
> 

Hmm. Yea, that's missing.

> - You allocate the pin_config, but you don't set the .name or .index fields.
> 

Ok

> Thanks,
> Richard
> 

Lets hold on this one until I can discuss with Maciej about what's missing here and what we need to add.

Thanks for the careful review, Richard!

Thanks,
Jake

  reply	other threads:[~2021-06-28 22:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 18:57 [PATCH net-next 0/5][pull request] 100GbE Intel Wired LAN Driver Updates 2021-06-25 Tony Nguyen
2021-06-25 18:57 ` [PATCH net-next 1/5] ice: add tracepoints Tony Nguyen
2021-06-25 18:57 ` [PATCH net-next 2/5] ice: add support for auxiliary input/output pins Tony Nguyen
2021-06-26 14:02   ` Richard Cochran
2021-06-28 22:45     ` Keller, Jacob E [this message]
2021-06-29 19:28       ` Keller, Jacob E
2021-06-29 19:32         ` Keller, Jacob E
2021-06-25 18:57 ` [PATCH net-next 3/5] ice: remove the VSI info from previous agg Tony Nguyen
2021-06-25 18:57 ` [PATCH net-next 4/5] ice: remove unnecessary VSI assignment Tony Nguyen
2021-06-25 18:57 ` [PATCH net-next 5/5] ice: Fix a memory leak in an error handling path in 'ice_pf_dcb_cfg()' Tony Nguyen
2021-06-25 19:10 ` [PATCH net-next 0/5][pull request] 100GbE Intel Wired LAN Driver Updates 2021-06-25 patchwork-bot+netdevbpf

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=fcc626d6773745ae9ecee10dfaca1316@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=maciej.machnikowski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.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).