| Age | Commit message (Collapse) | Author |
|---|
|
Now that comments can span multiple lines, add support for nested lists.
The yaml syntax is
comments:
- The BSP commit bundles 5 different changes:
- Disable SN65DSI86 GPIOs
- Disable scrambling (for V3U Falcon)
- Hot plug detectiong polling
- EDID retrieval
- 4k support for Display Port v1.2
which gets translated to
<ul>
<li>
<p>The BSP commit bundles 5 different changes</p>
<p>
<ul>
<li>
<p>Disable SN65DSI86 GPIOs</p>
</li>
<li>
<p>Disable scrambling (for V3U Falcon)</p>
</li>
<li>
<p>Hot plug detectiong polling</p>
</li>
<li>
<p>EDID retrieval</p>
</li>
<li>
<p>4k support for Display Port v1.2</p>
</li>
</ul>
</p>
</li>
</ul>
The YAML schema is relaxed accordingly to support sequences of anything
in comments.
Note the need for ':' at the end of the first line in the list. Without
that, the full comment will be treated as a single block of text by the
yaml parser, and the HTML generation script will render it as a single
paragraph without line breaks. This could be addressed, but if we keep
going further in that during, maybe a full markdown parser and generator
should be integrated instead.
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
|
|
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
|
|
Current periject is using bsp-commits tag,
but it is not enough to know each BSP status.
This patch replace it to bsp39x, and we will use bspXXX tag for BSP.
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
|
|
Add support for referring to posted patches and patch series
using Message-IDs, to be looked up in lore.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
|
|
The BSP repository was moved to github. The old repository lacks
several recent commits, leading to broken links in the HTML output (see
e.g. html/linux/io/bsp397_SDHI.html).
Update all BSP URLs to fix this. Note that BSP commits are opened in a
new tab, as github pages cannot be embedded in a frame.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
|
|
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
|
|
Use a regex rule to match patchwork instances within the schema. The
validator/title parser shall use the key as part of the URL to obtain
further patch information.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
This may be subject to further change so that we can ensure only one parent
exists, or that keys are unique in the dependencies list for example.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Provide the option to specify a URL or patchwork number reference.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Reduce the specific 'torvalds' and 'linux-next' sequences to mappings of
their own.
This allows the following syntax:
upstream:
- torvalds: 84df9525b0c27f3ebc2ebb1864fa62a97fdedb7d # Linux 4.19
- torvalds: 6d9666fb78526a7728cc4954ec1da4c2b416753d
- next: e0868bcfd529997cf98da1dd14bab8cb8175eda7
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Define the acceptable list of assignees, and remove the duplicated field.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Utilise pykwalify to provide a YAML schema for our data files. Define
an initial project schema under projects/ to define our data layout. An
example task data file is provided to demonstrate how the data could be
presented in text form.
A validator is provided which currently simply calls pykwalify. This is
just an initial demonstration of the validation process and can be
expanded upon later to provide automa{t,g}ic commit title processing,
and further business logic can be added with extra tools.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
