netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, jiri@mellanox.com,
	netdev@vger.kernel.org, oss-drivers@corigine.com,
	bijie.xu@corigine.com
Subject: Re: [PATCH net-next 0/2] net: minor kdoc fixes
Date: Tue, 03 Aug 2021 12:00:06 +0000	[thread overview]
Message-ID: <162799200642.3942.6713167878359867115.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210803094019.17291-1-simon.horman@corigine.com>

Hello:

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

On Tue,  3 Aug 2021 11:40:17 +0200 you wrote:
> Hi,
> 
> this short series fixes two kdoc errors that were noticed
> during development.
> 
> Bijie Xu (2):
>   net: flow_offload: correct comments mismatch with code
>   net: sched: provide missing kdoc for tcf_pkt_info and tcf_ematch_ops
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] net: flow_offload: correct comments mismatch with code
    https://git.kernel.org/netdev/net/c/c87a4c542b5a
  - [net-next,2/2] net: sched: provide missing kdoc for tcf_pkt_info and tcf_ematch_ops
    https://git.kernel.org/netdev/net/c/0161d151f3e3

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-08-03 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03  9:40 [PATCH net-next 0/2] net: minor kdoc fixes Simon Horman
2021-08-03  9:40 ` [PATCH net-next 1/2] net: flow_offload: correct comments mismatch with code Simon Horman
2021-08-03  9:40 ` [PATCH net-next 2/2] net: sched: provide missing kdoc for tcf_pkt_info and tcf_ematch_ops Simon Horman
2021-08-03 12:00 ` 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=162799200642.3942.6713167878359867115.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bijie.xu@corigine.com \
    --cc=davem@davemloft.net \
    --cc=jhs@mojatatu.com \
    --cc=jiri@mellanox.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=simon.horman@corigine.com \
    --cc=xiyou.wangcong@gmail.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 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).