From: patchwork-bot+netdevbpf@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: davem@davemloft.net, linux-nfc@lists.01.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
joe@perches.com
Subject: Re: [PATCH v2 1/2] nfc: mrvl: remove useless "continue" at end of loop
Date: Thu, 03 Jun 2021 21:10:05 +0000 [thread overview]
Message-ID: <162275460565.4513.18351247670919056182.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210602112011.44473-1-krzysztof.kozlowski@canonical.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 2 Jun 2021 13:20:10 +0200 you wrote:
> The "continue" statement at the end of a for loop does not have an
> effect. Entire loop contents can be slightly simplified to increase
> code readability. No functional change.
>
> Suggested-by: Joe Perches <joe@perches.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>
> [...]
Here is the summary with links:
- [v2,1/2] nfc: mrvl: remove useless "continue" at end of loop
https://git.kernel.org/netdev/net-next/c/a58224040f2d
- [v2,2/2] nfc: mrvl: reduce the scope of local variables
https://git.kernel.org/netdev/net-next/c/2c95e6c7e558
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-06-03 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 11:20 [PATCH v2 1/2] nfc: mrvl: remove useless "continue" at end of loop Krzysztof Kozlowski
2021-06-02 11:20 ` [PATCH v2 2/2] nfc: mrvl: reduce the scope of local variables Krzysztof Kozlowski
2021-06-03 21: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=162275460565.4513.18351247670919056182.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox