All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] examples/vdpa: fix spelling error in message
Date: Fri, 19 Oct 2018 10:20:53 -0700	[thread overview]
Message-ID: <20181019102053.4e59c2a9@xeon-e3> (raw)
In-Reply-To: <E923DB57A917B54B9182A2E928D00FA65E2EF652@IRSMSX102.ger.corp.intel.com>

On Thu, 18 Oct 2018 23:19:18 +0000
"Van Haaren, Harry" <harry.van.haaren@intel.com> wrote:

> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
> > Sent: Thursday, October 18, 2018 3:35 PM
> > To: dev@dpdk.org
> > Cc: Stephen Hemminger <stephen@networkplumber.org>
> > Subject: [dpdk-dev] [PATCH] examples/vdpa: fix spelling error in message
> > 
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> >  examples/vdpa/main.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/examples/vdpa/main.c b/examples/vdpa/main.c
> > index c5e8f58ec6d2..2ffbf2d8b4a3 100644
> > --- a/examples/vdpa/main.c
> > +++ b/examples/vdpa/main.c
> > @@ -334,7 +334,7 @@ static void cmd_create_vdpa_port_parsed(void
> > *parsed_result,
> >  	addr.type = PCI_ADDR;
> >  	did = rte_vdpa_find_device_id(&addr);
> >  	if (did < 0) {
> > -		cmdline_printf(cl, "Unable to find vdpa devide id.\n");
> > +		cmdline_printf(cl, "Unable to find vdpa divide id.\n");  
> 
> <nit>
>    I'd guess this fix was meant to be "device" not "divide".
> </nit>

Damn you autocorrect...

  reply	other threads:[~2018-10-19 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 22:34 [PATCH] examples/vdpa: fix spelling error in message Stephen Hemminger
2018-10-18 23:19 ` Van Haaren, Harry
2018-10-19 17:20   ` Stephen Hemminger [this message]
2018-10-22 13:53     ` Ferruh Yigit

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=20181019102053.4e59c2a9@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.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.