From: Simon Horman <horms@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: netdev@vger.kernel.org, jesse.brandeburg@intel.com,
edumazet@google.com, anthony.l.nguyen@intel.com, kuba@kernel.org,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next] ice: use list_for_each_entry() helper
Date: Wed, 2 Aug 2023 18:49:13 +0200 [thread overview]
Message-ID: <ZMqJCQC+8vL+HA5a@kernel.org> (raw)
In-Reply-To: <20230802090739.3266122-1-yangyingliang@huawei.com>
On Wed, Aug 02, 2023 at 05:07:39PM +0800, Yang Yingliang wrote:
> Convert list_for_each() to list_for_each_entry() where applicable.
> No functional changed.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: Simon Horman <horms@kernel.org>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next] ice: use list_for_each_entry() helper
Date: Wed, 2 Aug 2023 18:49:13 +0200 [thread overview]
Message-ID: <ZMqJCQC+8vL+HA5a@kernel.org> (raw)
In-Reply-To: <20230802090739.3266122-1-yangyingliang@huawei.com>
On Wed, Aug 02, 2023 at 05:07:39PM +0800, Yang Yingliang wrote:
> Convert list_for_each() to list_for_each_entry() where applicable.
> No functional changed.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-08-02 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 9:07 [Intel-wired-lan] [PATCH net-next] ice: use list_for_each_entry() helper Yang Yingliang
2023-08-02 9:07 ` Yang Yingliang
2023-08-02 16:49 ` Simon Horman [this message]
2023-08-02 16:49 ` Simon Horman
2023-08-11 6:50 ` [Intel-wired-lan] " Buvaneswaran, Sujai
2023-08-11 6:50 ` Buvaneswaran, Sujai
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=ZMqJCQC+8vL+HA5a@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yangyingliang@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 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.