All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiko Carstens <hca@linux.ibm.com>
Cc: wintera@linux.ibm.com, aswin@linux.ibm.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, linux-s390@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] drivers/s390/net: Enable CONTEXT_ANALYSIS
Date: Tue, 11 Aug 2026 00:20:10 +0000	[thread overview]
Message-ID: <178640761064.266182.4455560086468858785.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260805145032.1409325-1-hca@linux.ibm.com>

Hello:

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

On Wed,  5 Aug 2026 16:50:30 +0200 you wrote:
> Enable CONTEXT_ANALYSYS for drivers/s390/net.
> 
> Static code checking for acquiring and releasing locks used to be done
> with sparse. That was removed with [1] and replaced with a clang based
> approach [2]. The new approach requires that each subsystem needs to be
> explicitly enabled for checking.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] s390/ctcm: Add __context_unsafe() attribute to various functions
    https://git.kernel.org/netdev/net-next/c/4d422c526fcf
  - [net-next,2/2] drivers/s390/net: Enable CONTEXT_ANALYSIS
    https://git.kernel.org/netdev/net-next/c/5da9639bdd20

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



      parent reply	other threads:[~2026-08-11  0:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 14:50 [PATCH net-next 0/2] drivers/s390/net: Enable CONTEXT_ANALYSIS Heiko Carstens
2026-08-05 14:50 ` [PATCH net-next 1/2] s390/ctcm: Add __context_unsafe() attribute to various functions Heiko Carstens
2026-08-06 14:51   ` sashiko-bot
2026-08-05 14:50 ` [PATCH net-next 2/2] drivers/s390/net: Enable CONTEXT_ANALYSIS Heiko Carstens
2026-08-06 14:51   ` sashiko-bot
2026-08-05 15:50 ` [PATCH net-next 0/2] " Alexandra Winter
2026-08-07 12:57 ` Simon Horman
2026-08-11  0:20 ` 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=178640761064.266182.4455560086468858785.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=aswin@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hca@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wintera@linux.ibm.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.