b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
	b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH 1/6] batman-adv: Start new development cycle
Date: Fri, 20 Aug 2021 12:52:31 +0000	[thread overview]
Message-ID: <162946395159.27725.6381822484284696109.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210820083300.32289-2-sw@simonwunderlich.de>

Hello:

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

On Fri, 20 Aug 2021 10:32:55 +0200 you wrote:
> This version will contain all the (major or even only minor) changes for
> Linux 5.15.
> 
> The version number isn't a semantic version number with major and minor
> information. It is just encoding the year of the expected publishing as
> Linux -rc1 and the number of published versions this year (starting at 0).
> 
> [...]

Here is the summary with links:
  - [1/6] batman-adv: Start new development cycle
    https://git.kernel.org/netdev/net-next/c/53972e43d4a7
  - [2/6] batman-adv: Move IRC channel to hackint.org
    https://git.kernel.org/netdev/net-next/c/71d41c09f1fa
  - [3/6] batman-adv: Switch to kstrtox.h for kstrtou64
    https://git.kernel.org/netdev/net-next/c/70eeb75d4c4d
  - [4/6] batman-adv: Check ptr for NULL before reducing its refcnt
    https://git.kernel.org/netdev/net-next/c/6340dcbd6194
  - [5/6] batman-adv: Drop NULL check before dropping references
    https://git.kernel.org/netdev/net-next/c/79a0bffb835a
  - [6/6] batman-adv: bcast: remove remaining skb-copy calls
    https://git.kernel.org/netdev/net-next/c/808cfdfad579

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


  reply	other threads:[~2021-08-20 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20  8:32 [PATCH 0/6] (updated) pull request for net-next: batman-adv 2021-08-20 Simon Wunderlich
2021-08-20  8:32 ` [PATCH 1/6] batman-adv: Start new development cycle Simon Wunderlich
2021-08-20 12:52   ` patchwork-bot+netdevbpf [this message]
2021-08-20  8:32 ` [PATCH 2/6] batman-adv: Move IRC channel to hackint.org Simon Wunderlich
2021-08-20  8:32 ` [PATCH 3/6] batman-adv: Switch to kstrtox.h for kstrtou64 Simon Wunderlich
2021-08-20  8:32 ` [PATCH 4/6] batman-adv: Check ptr for NULL before reducing its refcnt Simon Wunderlich
2021-08-20  8:32 ` [PATCH 5/6] batman-adv: Drop NULL check before dropping references Simon Wunderlich
2021-08-20  8:33 ` [PATCH 6/6] batman-adv: bcast: remove remaining skb-copy calls Simon Wunderlich
  -- strict thread matches above, loose matches on Subject: below --
2023-11-15 17:59 [PATCH 0/6] pull request for net-next: batman-adv 2023-11-15 Simon Wunderlich
2023-11-15 17:59 ` [PATCH 1/6] batman-adv: Start new development cycle Simon Wunderlich
2023-11-18 17:50   ` patchwork-bot+netdevbpf
2021-08-19 15:33 [PATCH 0/6] pull request for net-next: batman-adv 2021-08-19 Simon Wunderlich
2021-08-19 15:33 ` [PATCH 1/6] batman-adv: Start new development cycle Simon Wunderlich

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=162946395159.27725.6381822484284696109.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sw@simonwunderlich.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).