Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de,
	geert@linux-m68k.org
Subject: Re: [Intel-wired-lan] [PATCH net v1] net: intel: fix old compiler regressions
Date: Wed, 07 Feb 2024 17:50:31 +0000	[thread overview]
Message-ID: <170732823192.3503.5684754555089844535.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240206022906.2194214-1-jesse.brandeburg@intel.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon,  5 Feb 2024 18:29:06 -0800 you wrote:
> The kernel build regressions/improvements email contained a couple of
> issues with old compilers (in fact all the reports were on different
> architectures, but all gcc 5.5) and the FIELD_PREP() and FIELD_GET()
> conversions. They're all because an integer #define that should have
> been declared as unsigned, was shifted to the point that it could set
> the sign bit.
> 
> [...]

Here is the summary with links:
  - [net,v1] net: intel: fix old compiler regressions
    https://git.kernel.org/netdev/net/c/75428f537d7c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2024-02-07 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06  2:29 [Intel-wired-lan] [PATCH net v1] net: intel: fix old compiler regressions Jesse Brandeburg
2024-02-07 17:50 ` patchwork-bot+netdevbpf [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=170732823192.3503.5684754555089844535.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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