From: patchwork-bot+netdevbpf@kernel.org
To: Tom Rix <trix@redhat.com>
Cc: claudiu.manoil@nxp.com, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gianfar: remove definition of DEBUG
Date: Sat, 16 Jan 2021 02:00:08 +0000 [thread overview]
Message-ID: <161076240872.31907.16057181697743328640.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210113215603.1721958-1-trix@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 13 Jan 2021 13:56:03 -0800 you wrote:
> From: Tom Rix <trix@redhat.com>
>
> Defining DEBUG should only be done in development.
> So remove DEBUG.
>
> Signed-off-by: Tom Rix <trix@redhat.com>
>
> [...]
Here is the summary with links:
- gianfar: remove definition of DEBUG
https://git.kernel.org/netdev/net-next/c/2267c530f868
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-01-16 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 21:56 [PATCH] gianfar: remove definition of DEBUG trix
2021-01-16 2: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=161076240872.31907.16057181697743328640.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trix@redhat.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.