All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alok Prasad <palok@marvell.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	aelior@marvell.com, pkushwaha@marvell.com,
	prabhakar.pkin@gmail.com
Subject: Re: [PATCH][v2] qed: Enhance rammod debug prints to provide pretty details
Date: Thu, 02 Dec 2021 12:30:10 +0000	[thread overview]
Message-ID: <163844821031.14016.14983197105837272875.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211202104156.17380-1-palok@marvell.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 2 Dec 2021 10:41:56 +0000 you wrote:
> From: Prabhakar Kushwaha <pkushwaha@marvell.com>
> 
> Instead of printing numbers of protocol IDs and rammod commands,
> enhance debug prints to provide names. s_protocol_types[] and
> s_ramrod_cmd_ids arrays[] are added to support along with APIs.
> 
> Signed-off-by: Ariel Elior <aelior@marvell.com>
> Signed-off-by: Alok Prasad <palok@marvell.com>
> Signed-off-by: Prabhakar Kushwaha <pkushwaha@marvell.com>
> 
> [...]

Here is the summary with links:
  - [v2] qed: Enhance rammod debug prints to provide pretty details
    https://git.kernel.org/netdev/net-next/c/7e9979e36007

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



      reply	other threads:[~2021-12-02 12:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 10:41 [PATCH][v2] qed: Enhance rammod debug prints to provide pretty details Alok Prasad
2021-12-02 12:30 ` 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=163844821031.14016.14983197105837272875.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aelior@marvell.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=palok@marvell.com \
    --cc=pkushwaha@marvell.com \
    --cc=prabhakar.pkin@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 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.