From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Lee Chee Yang <chee.yang.lee@intel.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 2/2] release-notes-5.0: update Repositories / Downloads section
Date: Tue, 30 Apr 2024 23:11:20 +0200 [thread overview]
Message-ID: <f0cb72f0-2799-4696-9291-30d85fbb0559@bootlin.com> (raw)
In-Reply-To: <20240430140017.1741751-2-chee.yang.lee@intel.com>
Hi Lee
On 4/30/24 at 16:00, Lee Chee Yang wrote:
> From: Lee Chee Yang <chee.yang.lee@intel.com>
>
> Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com>
Thanks for these updates.
For both patches:
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-04-30 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 14:00 [PATCH 1/2] migration-notes: add release notes for 4.0.18 chee.yang.lee
2024-04-30 14:00 ` [PATCH 2/2] release-notes-5.0: update Repositories / Downloads section chee.yang.lee
2024-04-30 21:11 ` Michael Opdenacker [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=f0cb72f0-2799-4696-9291-30d85fbb0559@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=chee.yang.lee@intel.com \
--cc=docs@lists.yoctoproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).