All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Julian Wiedmann <jwi@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	linux-s390@vger.kernel.org, hca@linux.ibm.com,
	kgraul@linux.ibm.com
Subject: Re: [PATCH net-next 0/2] s390/iucv: updates 2021-06-11
Date: Sat, 12 Jun 2021 20:10:03 +0000	[thread overview]
Message-ID: <162352860377.1274.17410671840872382469.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210611074502.1719233-1-jwi@linux.ibm.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Fri, 11 Jun 2021 09:45:00 +0200 you wrote:
> Hi Dave & Jakub,
> 
> please apply the following iucv patches to netdev's net-next tree.
> 
> This cleans up a pattern of forward declarations in two iucv drivers,
> so that they stop causing compile warnings with gcc11.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] net/af_iucv: clean up some forward declarations
    https://git.kernel.org/netdev/net-next/c/87c272c618c7
  - [net-next,2/2] s390/netiuvc: get rid of forward declarations
    https://git.kernel.org/netdev/net-next/c/fbf179683655

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



      parent reply	other threads:[~2021-06-12 20:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  7:45 [PATCH net-next 0/2] s390/iucv: updates 2021-06-11 Julian Wiedmann
2021-06-11  7:45 ` [PATCH net-next 1/2] net/af_iucv: clean up some forward declarations Julian Wiedmann
2021-06-11  7:45 ` [PATCH net-next 2/2] s390/netiuvc: get rid of " Julian Wiedmann
2021-06-12 20:10 ` 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=162352860377.1274.17410671840872382469.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=hca@linux.ibm.com \
    --cc=jwi@linux.ibm.com \
    --cc=kgraul@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-s390@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 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.