All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, Marc Dionne <marc.dionne@auristor.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Christian Brauner <brauner@kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>,
	linux-afs@lists.infradead.org, openafs-devel@openafs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 10/12] afs: Use rxgk RESPONSE to pass token for callback channel
Date: Mon, 7 Apr 2025 10:37:49 -0700	[thread overview]
Message-ID: <20250407103749.4e59159c@kernel.org> (raw)
In-Reply-To: <1349701.1744042902@warthog.procyon.org.uk>

On Mon, 07 Apr 2025 17:21:42 +0100 David Howells wrote:
> Simon Horman <horms@kernel.org> wrote:
> 
> > warning: format ‘%zx’ expects argument of type ‘size_t’, but argument 2 has type ‘long unsigned int’ [-Wformat=]  
> 
> I've fixed that and posted a v2.  I've also dealt with a bunch of kdoc
> warnings.

Please do follow the common netdev rules if the patches are targeting
net-next. We ask for new revisions not to be posted within 24h,
*ESPECIALLY* for trivial issues like compilation warnings :(
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#tl-dr
-- 
pv-bot: 24h

  reply	other threads:[~2025-04-07 17:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  9:14 [PATCH net-next 00/12] rxrpc, afs: Add AFS GSSAPI security class to AF_RXRPC and kafs David Howells
2025-04-07  9:14 ` [PATCH net-next 01/12] rxrpc: Pull out certain app callback funcs into an ops table David Howells
2025-04-07  9:14 ` [PATCH net-next 02/12] rxrpc: Allow CHALLENGEs to the passed to the app for a RESPONSE David Howells
2025-04-07  9:14 ` [PATCH net-next 03/12] rxrpc: Add the security index for yfs-rxgk David Howells
2025-04-07  9:14 ` [PATCH net-next 04/12] rxrpc: Add YFS RxGK (GSSAPI) security class David Howells
2025-04-07  9:14 ` [PATCH net-next 05/12] rxrpc: rxgk: Provide infrastructure and key derivation David Howells
2025-04-07  9:14 ` [PATCH net-next 06/12] rxrpc: rxgk: Implement the yfs-rxgk security class (GSSAPI) David Howells
2025-04-07  9:14 ` [PATCH net-next 07/12] rxrpc: rxgk: Implement connection rekeying David Howells
2025-04-07  9:14 ` [PATCH net-next 08/12] rxrpc: Allow the app to store private data on peer structs David Howells
2025-04-07  9:14 ` [PATCH net-next 09/12] rxrpc: Display security params in the afs_cb_call tracepoint David Howells
2025-04-07  9:14 ` [PATCH net-next 10/12] afs: Use rxgk RESPONSE to pass token for callback channel David Howells
2025-04-07 16:12   ` Simon Horman
2025-04-07 16:21     ` David Howells
2025-04-07 17:37       ` Jakub Kicinski [this message]
2025-04-07  9:14 ` [PATCH net-next 11/12] rxrpc: Add more CHALLENGE/RESPONSE packet tracing David Howells
2025-04-07  9:14 ` [PATCH net-next 12/12] rxrpc: rxperf: Add test RxGK server keys David Howells

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=20250407103749.4e59159c@kernel.org \
    --to=kuba@kernel.org \
    --cc=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=netdev@vger.kernel.org \
    --cc=openafs-devel@openafs.org \
    --cc=pabeni@redhat.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.