From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Dheeraj Reddy Jonnalagadda <dheeraj.linuxdev@gmail.com>
Cc: Simon Horman <horms@kernel.org>,
<michal.swiatkowski@linux.intel.com>,
<anthony.l.nguyen@intel.com>, <piotr.kwapulinski@intel.com>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 net-next] ixgbe: Fix endian handling for ACI descriptor registers
Date: Mon, 27 Jan 2025 12:30:17 +0100 [thread overview]
Message-ID: <2f12d571-44bd-4737-a6df-e9d11a0a9c78@intel.com> (raw)
In-Reply-To: <Z4+mH7s/YnfdXgJ5@HOME-PC>
On 1/21/25 14:50, Dheeraj Reddy Jonnalagadda wrote:
>>
>> @Dheeraj, do you want to hone your minimal fix to avoid sparse warnings?
>
> Sure, I will update the patch to avoid sparse warnings.
>
>> follow up question: do you want to proceed with a full conversion?
>>
>> @Michal is going to send patches that depend on this "full conversion"
>> next month, so he could also take care of the "full conversion".
>
> I don't mind sending a patch with the full conversion. Although that
> would have quite a few changes. To clarify
>
> 1. Are we updating both @reg and @value to be __le32 ?
> 2. Should we also update ixgbe_read_reg() to also handle and return
> __le32 values?
>
> -Dheeraj
Hi, noone objected, so the answer is 2 x Yes
next prev parent reply other threads:[~2025-01-27 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 3:41 [PATCH v2 net-next] ixgbe: Fix endian handling for ACI descriptor registers Dheeraj Reddy Jonnalagadda
2025-01-15 5:55 ` Michal Swiatkowski
2025-01-15 11:39 ` Kwapulinski, Piotr
2025-01-16 16:21 ` Simon Horman
2025-01-17 10:01 ` Przemek Kitszel
2025-01-17 18:09 ` Simon Horman
2025-01-20 14:48 ` Przemek Kitszel
2025-01-21 13:50 ` Dheeraj Reddy Jonnalagadda
2025-01-27 11:30 ` Przemek Kitszel [this message]
2025-01-18 15:05 ` kernel test robot
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=2f12d571-44bd-4737-a6df-e9d11a0a9c78@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dheeraj.linuxdev@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=piotr.kwapulinski@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 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).