From: David Miller <davem@davemloft.net>
To: gregory.clement@bootlin.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
alexandre.belloni@bootlin.com
Subject: Re: [PATCH] net: mscc: ocelot: Fix comment in ocelot_vlant_wait_for_completion()
Date: Wed, 17 Oct 2018 22:34:02 -0700 (PDT) [thread overview]
Message-ID: <20181017.223402.1520667880142559637.davem@davemloft.net> (raw)
In-Reply-To: <20181017152635.22981-1-gregory.clement@bootlin.com>
From: Gregory CLEMENT <gregory.clement@bootlin.com>
Date: Wed, 17 Oct 2018 17:26:35 +0200
> The ocelot_vlant_wait_for_completion() function is very similar to the
> ocelot_mact_wait_for_completion(). It seemed to have be copied but the
> comment was not updated, so let's fix it.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Applied.
prev parent reply other threads:[~2018-10-18 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 15:26 [PATCH] net: mscc: ocelot: Fix comment in ocelot_vlant_wait_for_completion() Gregory CLEMENT
2018-10-18 5:34 ` David Miller [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=20181017.223402.1520667880142559637.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.belloni@bootlin.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).