netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	jk@codeconstruct.com.au, stefan@datenfreihafen.org,
	j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
	oliver@neukum.org, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
	alex.aring@gmail.com, jukka.rissanen@linux.intel.com,
	matt@codeconstruct.com.au, linux-usb@vger.kernel.org,
	linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: don't include ndisc.h from ipv6.h
Date: Sat, 05 Feb 2022 03:50:08 +0000	[thread overview]
Message-ID: <164403300852.24542.401822864711989941.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220203231240.2297588-1-kuba@kernel.org>

Hello:

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

On Thu,  3 Feb 2022 15:12:40 -0800 you wrote:
> Nothing in ipv6.h needs ndisc.h, drop it.
> 
> Link: https://lore.kernel.org/r/20220203043457.2222388-1-kuba@kernel.org
> Acked-by: Jeremy Kerr <jk@codeconstruct.com.au>
> Acked-by: Stefan Schmidt <stefan@datenfreihafen.org>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: don't include ndisc.h from ipv6.h
    https://git.kernel.org/netdev/net-next/c/c78b8b20e349

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



      parent reply	other threads:[~2022-02-05  3:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 23:12 [PATCH net-next v2] net: don't include ndisc.h from ipv6.h Jakub Kicinski
2022-02-04  4:09 ` David Ahern
2022-02-05  3: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=164403300852.24542.401822864711989941.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alex.aring@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=j.vosburgh@gmail.com \
    --cc=jk@codeconstruct.com.au \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=stefan@datenfreihafen.org \
    --cc=vfalico@gmail.com \
    --cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).