All of lore.kernel.org
 help / color / mirror / Atom feed
From: guang_feng_wang@163.com
To: jan.kiszka@siemens.com, rpm@xenomai.org, florian.bezdeka@siemens.com
Cc: xenomai@lists.linux.dev, guang feng wang <guang_feng_wang@163.com>
Subject: [PATCH website v1 0/5] doc: refresh Cobalt installation guide
Date: Sun, 28 Jun 2026 12:50:54 +0800	[thread overview]
Message-ID: <cover.1782585785.git.guang_feng_wang@163.com> (raw)

From: guang feng wang <guang_feng_wang@163.com>

Hi,

This series updates a few stale I-pipe-era references in the Xenomai 3
installation guide, mainly around the Cobalt setup path.

The page already documents Dovetail as a Cobalt-specific requirement,
but a few examples still refer to legacy I-pipe references.

The changes are limited to the following patches:

guang feng wang (5):
  doc: replace legacy I-pipe usage with Dovetail
  doc: update stale Cobalt kernel preparation example
  doc: mark old PowerPC and ARM build examples as historical
  doc: generalize ARM64 Cobalt build notes
  doc: update Cobalt boot log

 content/installation/_index.md | 39 ++++++++++++++++++++--------------
 1 file changed, 23 insertions(+), 16 deletions(-)

-- 
2.34.1


             reply	other threads:[~2026-06-28  4:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-28  4:50 guang_feng_wang [this message]
2026-06-28  4:50 ` [PATCH website v1 1/5] doc: replace legacy I-pipe usage with Dovetail guang_feng_wang
2026-06-28  4:50 ` [PATCH website v1 2/5] doc: update stale Cobalt kernel preparation example guang_feng_wang
2026-06-28  4:50 ` [PATCH website v1 3/5] doc: mark old PowerPC and ARM build examples as historical guang_feng_wang
2026-06-28  4:50 ` [PATCH website v1 4/5] doc: generalize ARM64 Cobalt build notes guang_feng_wang
2026-06-28  4:50 ` [PATCH website v1 5/5] doc: update Cobalt boot log guang_feng_wang

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=cover.1782585785.git.guang_feng_wang@163.com \
    --to=guang_feng_wang@163.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=rpm@xenomai.org \
    --cc=xenomai@lists.linux.dev \
    /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.