From: Leon Romanovsky <leon@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Karsten Keil <isdn@linux-pingi.de>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1] mISDN: Remove obsolete PIPELINE_DEBUG debugging information
Date: Thu, 20 May 2021 11:49:36 +0300 [thread overview]
Message-ID: <YKYioHWGxUrdMogL@unreal> (raw)
In-Reply-To: <20210520021412.8100-2-thunder.leizhen@huawei.com>
On Thu, May 20, 2021 at 10:14:11AM +0800, Zhen Lei wrote:
> As Leon Romanovsky's tips:
> The definition of macro PIPELINE_DEBUG is commented more than 10 years ago
> and can be seen as a dead code that should be removed.
>
> Suggested-by: Leon Romanovsky <leon@kernel.org>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> drivers/isdn/mISDN/dsp_pipeline.c | 46 ++-----------------------------
> 1 file changed, 2 insertions(+), 44 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2021-05-20 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 2:14 [PATCH 0/1] mISDN: Remove obsolete PIPELINE_DEBUG debugging information Zhen Lei
2021-05-20 2:14 ` [PATCH 1/1] " Zhen Lei
2021-05-20 8:49 ` Leon Romanovsky [this message]
2021-05-20 20:10 ` [PATCH 0/1] " patchwork-bot+netdevbpf
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=YKYioHWGxUrdMogL@unreal \
--to=leon@kernel.org \
--cc=isdn@linux-pingi.de \
--cc=netdev@vger.kernel.org \
--cc=thunder.leizhen@huawei.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).