BMC/tmp/openbmc.git/meta-phosphor/scripts, branch fplus

meta-phosphor: run-repotest: ensure fail on supported-machine.md

2024-11-20T15:23:08+00:00

run-repotest is currently not failing when the `supported-machines.md` needs an update. Add an `exit 1` so that this fails visibly rather than just reporting a warning. Signed-off-by: Patrick Williams Change-Id: Idd3332e4433b4d9b4792d6d1bfef8911930e4ffa

meta-phosphor: generate supported machine list

2024-09-05T02:44:12+00:00

Add a script to generate a list of supported machines and hook it into the `run-repotest` to ensure that it is ran as necessary when new machines are added or removed. Fixes openbmc/openbmc#3926. Signed-off-by: Patrick Williams Change-Id: If33aa08451bb8a789459bf49d8d7ec9044973304

meta-bytedance: g220a: linux: Remove patch

2024-07-10T12:21:06+00:00

The driver is already in upstream, remove it. Signed-off-by: Lei YU Change-Id: I58384e3127694e5cda1d484c7eeb29d1d843ff7d

meta-phosphor: repotest: prohibit new DTS files

2024-01-02T17:33:32+00:00

DTS files should be submitted upstream to the kernel, just like patches. Allowing individual DTS files to be added to the tree is just another form of patching the kernel. Explicitly search and prohibit new ones from being added. Signed-off-by: Patrick Williams Change-Id: Ibd176423cda5082ead3bf1d3da1e66507e0ea475

meta-aspeed: Fix value_start issue in `rev_id` path

2023-09-01T02:44:29+00:00

There's a bug in socsec that prevents the IBM's configuration from successfully building an OTP image. I have got the fix merged upstream: https://github.com/AspeedTech-BMC/socsec/pull/18 However, Aspeed do not plan on doing a release until October: > [ 17:51 ] arj: @Troy Lee any chance Neal can tag a new socsec release so we can bump it in OpenBMC and pick up some recent fixes? > [ 18:25 ] Troy Lee: Current schedule is October. https://discord.com/channels/775381525260664832/922871693008068638/1144547174286377062 For now, fix otptool using a recipe patch, in violation of the usual guidelines. I prefer we do this over switching to a "git" version for the recipe as instability with these tools really cannot be tolerated. Change-Id: I65b1992b5479ea257cfa65fd8b3cfc021b7d3dea Signed-off-by: Andrew Jeffery

meta-phosphor: run-repotest: Remove meta-google shellcheck exceptions

2023-06-06T14:16:01+00:00

Change-Id: I7e5087f65512610b75631174dd4175f1b07f4284 Signed-off-by: William A. Kennington III

meta-ibm: fix some shellcheck issues

2023-06-05T23:58:41+00:00

Signed-off-by: Patrick Williams Change-Id: I3792c2aa7f4bcd92254717c5bd00bc438f9101be

meta-inventec: remove stray repotest exemptions

2023-06-03T00:45:45+00:00

Signed-off-by: Patrick Williams Change-Id: Ie1fd5cddb2f449bd85385a5a50143b2261213ea5

meta-quanta: fix shellcheck issues

2023-04-27T16:16:12+00:00

Signed-off-by: Patrick Williams Change-Id: I189baf142cc86d44ebbf615edd3bb0ec1785be8d

meta-openpower: fix shellcheck issues

2023-04-20T11:36:29+00:00

Signed-off-by: Patrick Williams Change-Id: I35a9ffed937919467dec62a1fbff729f4a51366c