All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] ref/dev-manual: Update multiconfig documentation
Date: Mon, 13 Jun 2022 14:56:30 +0100	[thread overview]
Message-ID: <38c002186fe2157ba4cd5a9372e97057c9ac1164.camel@linuxfoundation.org> (raw)
In-Reply-To: <d67b1d84-86e5-c784-5965-9fce2c7e1666@bootlin.com>

On Fri, 2022-06-10 at 19:42 +0200, Michael Opdenacker wrote:
> Hi Richard,
> 
> Thanks a lot for the update!
> 
> On 6/9/22 11:40, Richard Purdie wrote:
> > +   The configuration definitions are implmentation dependency but often
> 
> Did you mean "are implementation dependent"?
> I'll be happy to fix this by myself.

Correct, thanks!

Cheers,

Richard


      reply	other threads:[~2022-06-13 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  9:40 [PATCH] ref/dev-manual: Update multiconfig documentation Richard Purdie
2022-06-09 13:00 ` [docs] " Marta Rybczynska
2022-06-10 17:42 ` Michael Opdenacker
2022-06-13 13:56   ` Richard Purdie [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=38c002186fe2157ba4cd5a9372e97057c9ac1164.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.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.