All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Pawel Kaminski <pawel.kaminski@intel.com>
Cc: intel-wired-lan@osuosl.org,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1] ice: Improve logs for max ntuple errors
Date: Wed, 22 Nov 2023 19:14:12 +0000	[thread overview]
Message-ID: <20231122191412.GC6731@kernel.org> (raw)
In-Reply-To: <20231121013206.2321-1-pawel.kaminski@intel.com>

On Mon, Nov 20, 2023 at 05:32:06PM -0800, Pawel Kaminski wrote:
> Supported number of ntuple filters affect also maximum location value that
> can be provided to ethtool command. Update error message to provide info
> about max supported value.
> 
> Fix double spaces in the error messages.
> 
> Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> Signed-off-by: Pawel Kaminski <pawel.kaminski@intel.com>

Reviewed-by: Simon Horman <horms@kernel.org>

...
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Pawel Kaminski <pawel.kaminski@intel.com>
Cc: intel-wired-lan@osuosl.org, netdev@vger.kernel.org,
	Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [PATCH iwl-next v1] ice: Improve logs for max ntuple errors
Date: Wed, 22 Nov 2023 19:14:12 +0000	[thread overview]
Message-ID: <20231122191412.GC6731@kernel.org> (raw)
In-Reply-To: <20231121013206.2321-1-pawel.kaminski@intel.com>

On Mon, Nov 20, 2023 at 05:32:06PM -0800, Pawel Kaminski wrote:
> Supported number of ntuple filters affect also maximum location value that
> can be provided to ethtool command. Update error message to provide info
> about max supported value.
> 
> Fix double spaces in the error messages.
> 
> Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> Signed-off-by: Pawel Kaminski <pawel.kaminski@intel.com>

Reviewed-by: Simon Horman <horms@kernel.org>

...

  reply	other threads:[~2023-11-22 19:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21  1:32 [Intel-wired-lan] [PATCH iwl-next v1] ice: Improve logs for max ntuple errors Pawel Kaminski
2023-11-21  1:32 ` Pawel Kaminski
2023-11-22 19:14 ` Simon Horman [this message]
2023-11-22 19:14   ` Simon Horman
2023-11-28 14:21 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-11-28 14:21   ` Pucha, HimasekharX Reddy

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=20231122191412.GC6731@kernel.org \
    --to=horms@kernel.org \
    --cc=intel-wired-lan@osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.kaminski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.