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 net-next v1] iavf: Add support for 50G/100G in AIM algorithm
Date: Thu, 16 Sep 2021 22:07:04 +0000	[thread overview]
Message-ID: <02f5ca336393cd78b0fe366a85bc4f75c935b226.camel@intel.com> (raw)
In-Reply-To: <20210915091559.27096-1-mateusz.palczewski@intel.com>

On Wed, 2021-09-15 at 11:15 +0200, Mateusz Palczewski wrote:
> Advanced link speed support was added long back, but adding AIM
> support
> was missed. Adding AIM support for advanced link speed support
> allows the algorithm to take into account 50G/100G link speeds.
> Also, other previous speeds are taken into consideration when
> advanced
> link speeds are supported.
> 
> Signed-off-by: Brett Creeley <brett.creeley@intel.com>
> Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>

This has build issues:

../drivers/net/ethernet/intel/iavf/iavf_txrx.c:404:1: error: stray \342
in program
 <200b>
 ^
../drivers/net/ethernet/intel/iavf/iavf_txrx.c:404:2: error: stray \200
in program
 <200b>
  ^
../drivers/net/ethernet/intel/iavf/iavf_txrx.c:404:3: error: stray \213
in program
 <200b>
   ^
../drivers/net/ethernet/intel/iavf/iavf_txrx.c:422:1: error: stray \342
in program
 <200b>
 ^
../drivers/net/ethernet/intel/iavf/iavf_txrx.c:422:2: error: stray \200
in program
 <200b>
  ^
../drivers/net/ethernet/intel/iavf/iavf_txrx.c:422:3: error: stray \213
in program
 <200b>
   ^


      reply	other threads:[~2021-09-16 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15  9:15 [Intel-wired-lan] [PATCH net-next v1] iavf: Add support for 50G/100G in AIM algorithm Mateusz Palczewski
2021-09-16 22:07 ` Nguyen, Anthony L [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=02f5ca336393cd78b0fe366a85bc4f75c935b226.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