mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Augusto Mecking Caringi <augustocaringi@gmail.com>,
	Colin King <colin.king@canonical.com>
Cc: Fugang Duan <fugang.duan@nxp.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: fec: fix spelling mistake "coalesed" -> "coalesced"
Date: Sat, 04 Jun 2016 23:36:35 -0700	[thread overview]
Message-ID: <1465108595.11800.55.camel@perches.com> (raw)
In-Reply-To: <CADFy_4GNq-VQj5kgFsoCiHJTHTo21ZdjijfD=mEM602YCrewEw@mail.gmail.com>

On Sat, 2016-06-04 at 16:43 -0300, Augusto Mecking Caringi wrote:
> On Sat, Jun 4, 2016 at 4:01 PM, Colin King <colin.king@canonical.com> wrote:
> > From: Colin Ian King <colin.king@canonical.com>
> > trivial fix to spelling mistake in pr_err message
[]
> > diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
[]
> > @@ -2427,13 +2427,13 @@ fec_enet_set_coalesce(struct net_device *ndev, struct ethtool_coalesce *ec)
> > 
> >         cycle = fec_enet_us_to_itr_clock(ndev, fep->rx_time_itr);
> >         if (cycle > 0xFFFF) {
> > -               pr_err("Rx coalesed usec exceeed hardware limiation");
> > +               pr_err("Rx coalesced usec exceeed hardware limiation");
> >                 return -EINVAL;
> >         }
> > 
> >         cycle = fec_enet_us_to_itr_clock(ndev, fep->tx_time_itr);
> >         if (cycle > 0xFFFF) {
> > -               pr_err("Rx coalesed usec exceeed hardware limiation");
> > +               pr_err("Rx coalesced usec exceeed hardware limiation");
> >                 return -EINVAL;
> >         }
> > 
> s/limiation/limitation

Could also add \n terminations to the pr_err uses.

  reply	other threads:[~2016-06-05  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-04 19:01 Colin King
2016-06-04 19:43 ` Augusto Mecking Caringi
2016-06-05  6:36   ` Joe Perches [this message]
2016-06-06  2:13 ` Fugang Duan

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=1465108595.11800.55.camel@perches.com \
    --to=joe@perches.com \
    --cc=augustocaringi@gmail.com \
    --cc=colin.king@canonical.com \
    --cc=fugang.duan@nxp.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

all inboxes | Powered by JetHome®