All of lore.kernel.org
 help / color / mirror / Atom feed
From: "naamax.meir" <naamax.meir@linux.intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	intel-wired-lan@lists.osuosl.org
Cc: przemyslaw.kitszel@intel.com, marcin.szycik@linux.intel.com,
	netdev@vger.kernel.org, horms@kernel.org,
	aleksander.lobakin@intel.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 01/15] e1000e: make lost bits explicit
Date: Tue, 19 Dec 2023 09:57:46 +0200	[thread overview]
Message-ID: <ee1112af-cb13-483b-b6b5-4489a39c57cc@linux.intel.com> (raw)
In-Reply-To: <20231206010114.2259388-2-jesse.brandeburg@intel.com>

On 12/6/2023 03:01, Jesse Brandeburg wrote:
> For more than 15 years this code has passed in a request for a page and
> masked off that page when read/writing. This code has been here forever,
> but FIELD_PREP finds the bug when converted to use it. Change the code
> to do exactly the same thing but allow the conversion to FIELD_PREP in a
> later patch. To make it clear what we lost when making this change I
> left a comment, but there is no point to change the code to generate a
> correct sequence at this point.
> 
> This is not a Fixes tagged patch on purpose because it doesn't change
> the binary output.
> 
> Reviewed-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> ---
>   drivers/net/ethernet/intel/e1000e/80003es2lan.c | 13 +++++++------
>   1 file changed, 7 insertions(+), 6 deletions(-)

Tested-by: Naama Meir <naamax.meir@linux.intel.com>
_______________________________________________
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: "naamax.meir" <naamax.meir@linux.intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	intel-wired-lan@lists.osuosl.org
Cc: przemyslaw.kitszel@intel.com, aleksander.lobakin@intel.com,
	marcin.szycik@linux.intel.com, horms@kernel.org,
	netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 01/15] e1000e: make lost bits explicit
Date: Tue, 19 Dec 2023 09:57:46 +0200	[thread overview]
Message-ID: <ee1112af-cb13-483b-b6b5-4489a39c57cc@linux.intel.com> (raw)
In-Reply-To: <20231206010114.2259388-2-jesse.brandeburg@intel.com>

On 12/6/2023 03:01, Jesse Brandeburg wrote:
> For more than 15 years this code has passed in a request for a page and
> masked off that page when read/writing. This code has been here forever,
> but FIELD_PREP finds the bug when converted to use it. Change the code
> to do exactly the same thing but allow the conversion to FIELD_PREP in a
> later patch. To make it clear what we lost when making this change I
> left a comment, but there is no point to change the code to generate a
> correct sequence at this point.
> 
> This is not a Fixes tagged patch on purpose because it doesn't change
> the binary output.
> 
> Reviewed-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> ---
>   drivers/net/ethernet/intel/e1000e/80003es2lan.c | 13 +++++++------
>   1 file changed, 7 insertions(+), 6 deletions(-)

Tested-by: Naama Meir <naamax.meir@linux.intel.com>

  reply	other threads:[~2023-12-19  7:58 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  1:00 [Intel-wired-lan] [PATCH iwl-next v2 00/15] intel: use bitfield operations Jesse Brandeburg
2023-12-06  1:00 ` Jesse Brandeburg
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 01/15] e1000e: make lost bits explicit Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-19  7:57   ` naamax.meir [this message]
2023-12-19  7:57     ` [Intel-wired-lan] " naamax.meir
2023-12-25  9:36   ` Simon Horman
2023-12-25  9:36     ` Simon Horman
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 02/15] intel: add bit macro includes where needed Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-25  9:35   ` [Intel-wired-lan] " Simon Horman
2023-12-25  9:35     ` Simon Horman
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 03/15] intel: legacy: field prep conversion Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-13  2:58   ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-12-13  2:58     ` Pucha, HimasekharX Reddy
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 04/15] i40e: " Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-13  2:58   ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-12-13  2:58     ` Pucha, HimasekharX Reddy
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 05/15] iavf: " Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-14 13:08   ` [Intel-wired-lan] " Romanowski, Rafal
2023-12-14 13:08     ` Romanowski, Rafal
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 06/15] ice: " Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-13  2:58   ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-12-13  2:58     ` Pucha, HimasekharX Reddy
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 07/15] ice: fix pre-shifted bit usage Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-13  2:57   ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-12-13  2:57     ` Pucha, HimasekharX Reddy
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 08/15] igc: field prep conversion Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 09/15] intel: legacy: field get conversion Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-13  2:57   ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-12-13  2:57     ` Pucha, HimasekharX Reddy
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 10/15] igc: " Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 11/15] i40e: " Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-13  2:57   ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-12-13  2:57     ` Pucha, HimasekharX Reddy
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 12/15] iavf: " Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-14 13:10   ` [Intel-wired-lan] " Romanowski, Rafal
2023-12-14 13:10     ` Romanowski, Rafal
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 13/15] ice: " Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-13  2:57   ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-12-13  2:57     ` Pucha, HimasekharX Reddy
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 14/15] ice: cleanup inconsistent code Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-13  2:57   ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-12-13  2:57     ` Pucha, HimasekharX Reddy
2023-12-13  4:06   ` Kalesh Anakkur Purayil
2023-12-13  4:06     ` Kalesh Anakkur Purayil
2023-12-13 18:27     ` [Intel-wired-lan] " Jesse Brandeburg
2023-12-13 18:27       ` Jesse Brandeburg
2023-12-14  3:26       ` [Intel-wired-lan] " Kalesh Anakkur Purayil
2023-12-14  3:26         ` Kalesh Anakkur Purayil
2023-12-14  7:16       ` [Intel-wired-lan] " Przemek Kitszel
2023-12-14  7:16         ` Przemek Kitszel
2023-12-25  9:37         ` [Intel-wired-lan] " Simon Horman
2023-12-25  9:37           ` Simon Horman
2023-12-06  1:01 ` [Intel-wired-lan] [PATCH iwl-next v2 15/15] idpf: refactor some missing field get/prep conversions Jesse Brandeburg
2023-12-06  1:01   ` Jesse Brandeburg
2023-12-22 18:48   ` [Intel-wired-lan] " Register, Scott
2023-12-22 18:48     ` Register, Scott
2023-12-25  9:36   ` Simon Horman
2023-12-25  9:36     ` Simon Horman
2023-12-14 13:09 ` [Intel-wired-lan] [PATCH iwl-next v2 00/15] intel: use bitfield operations Romanowski, Rafal
2023-12-14 13:09   ` Romanowski, Rafal

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=ee1112af-cb13-483b-b6b5-4489a39c57cc@linux.intel.com \
    --to=naamax.meir@linux.intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=marcin.szycik@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@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.