From: Jakub Kicinski <kuba@kernel.org>
To: Zhongjun Tan <hbut_tan@163.com>
Cc: jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Zhongjun Tan <tanzhongjun@coolpad.com>
Subject: Re: [PATCH] iavf: Remove condition with no effect
Date: Fri, 8 Jul 2022 15:14:22 -0700 [thread overview]
Message-ID: <20220708151422.57456006@kernel.org> (raw)
In-Reply-To: <20220708035154.44079-1-hbut_tan@163.com>
On Fri, 8 Jul 2022 11:51:54 +0800 Zhongjun Tan wrote:
> From: Zhongjun Tan <tanzhongjun@coolpad.com>
>
> Remove condition with no effect
The code is fine, please fix the tool you're using to not generate such
patches.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Zhongjun Tan <hbut_tan@163.com>
Cc: netdev@vger.kernel.org, jesse.brandeburg@intel.com,
Zhongjun Tan <tanzhongjun@coolpad.com>,
linux-kernel@vger.kernel.org, edumazet@google.com,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH] iavf: Remove condition with no effect
Date: Fri, 8 Jul 2022 15:14:22 -0700 [thread overview]
Message-ID: <20220708151422.57456006@kernel.org> (raw)
In-Reply-To: <20220708035154.44079-1-hbut_tan@163.com>
On Fri, 8 Jul 2022 11:51:54 +0800 Zhongjun Tan wrote:
> From: Zhongjun Tan <tanzhongjun@coolpad.com>
>
> Remove condition with no effect
The code is fine, please fix the tool you're using to not generate such
patches.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-07-08 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 3:51 [PATCH] iavf: Remove condition with no effect Zhongjun Tan
2022-07-08 3:51 ` [Intel-wired-lan] " Zhongjun Tan
2022-07-08 22:14 ` Jakub Kicinski [this message]
2022-07-08 22:14 ` Jakub Kicinski
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=20220708151422.57456006@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hbut_tan@163.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tanzhongjun@coolpad.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.