DPDK patches and discussions
 help / color / mirror / Atom feed
From: Josh Soref <jsoref@gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	dev@dpdk.org,  David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] Spelling
Date: Mon, 29 Nov 2021 09:12:53 -0500	[thread overview]
Message-ID: <CACZqfqBXnVb4j+BfrZBgaMQoZvM1vkAhkXv1uXwNDhyro1Pykw@mail.gmail.com> (raw)
In-Reply-To: <68412427-b6aa-cb38-110a-14bc90d8fdc0@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]

On Mon, Nov 29, 2021, 9:05 AM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 11/29/2021 1:59 PM, Bruce Richardson wrote:
> > On Mon, Nov 29, 2021 at 12:49:56PM +0000, Ferruh Yigit wrote:
> >> Hi Josh, Thanks for the patch.
> >>
> >> The typo fixes for comments and logs are more straightforward, but I
> have
> >> mixed feeling about the variable / macro typo fixes, let's see what
> others
> >> think.
> >>
> >> And I think we should get this patch either one of the first patch or
> last
> >> patch to prevent conflict with other patches.
> >
> > +1 to being a first patch to start things off clean.
> >
> > For the macros, since there is quick a bit of content in the patch, could
> > we have the patch split into a separate patch for macro changes to review
> > separately, allowing the simple doc/printf spelling changes to go in
> > immediately?
>

Yeah, this is doable. I'll see if I can do it now. It's a lot of files,
plus I'll need to figure out the command sequence to reply to this thread.
If someone is available on Slack for some handholding, that might help me
get it done faster.

Also as far as I can see there are multiple build errors related to the
> variable / macro renames, which was the concern.
>

I'm used to having access to GitHub based CI that let me test before making
a PR. I've locally dropped the peer change, but didn't resubmit since I
figured I'd wait for replies.

(Last night I installed meson and ninja, so I might be able to do a local
build.)

>

[-- Attachment #2: Type: text/html, Size: 2421 bytes --]

  reply	other threads:[~2021-11-29 19:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26 19:58 Josh Soref
2021-11-29 12:49 ` Ferruh Yigit
2021-11-29 13:59   ` Bruce Richardson
2021-11-29 14:02     ` Thomas Monjalon
2021-11-29 18:11       ` Ajit Khaparde
2021-11-29 14:03     ` Ferruh Yigit
2021-11-29 14:12       ` Josh Soref [this message]
2021-11-29 14:47         ` Bruce Richardson
2021-11-29 14:52         ` Ferruh Yigit
2021-11-29 16:08 ` [PATCH v2] Spelling comments/text Josh Soref
2022-01-06 16:46   ` Thomas Monjalon
2022-01-11 10:51     ` Thomas Monjalon
2022-01-11 14:00       ` Kevin Traynor
2022-01-11 14:23         ` Thomas Monjalon
2022-01-06 16:52   ` Thomas Monjalon
2022-01-07 11:23     ` Bruce Richardson
2022-01-07 14:58       ` Thomas Monjalon
2022-01-07 15:04         ` Josh Soref
2022-01-07 15:28         ` Bruce Richardson
2022-01-07 16:27           ` Morten Brørup
2022-01-07 16:37             ` Bruce Richardson

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=CACZqfqBXnVb4j+BfrZBgaMQoZvM1vkAhkXv1uXwNDhyro1Pykw@mail.gmail.com \
    --to=jsoref@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    /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).