Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / infra / proto / a603eb5751a34bb142f5976e1d0b214bcec70088
commita603eb5751a34bb142f5976e1d0b214bcec70088[log] [tgz]
authorYH Lin <yueherngl@google.com>Thu Oct 05 15:59:21 2023 +0000
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Oct 05 21:06:01 2023 +0000
treeda36d6353cbcc28295593c13ecd1c2a30944047b
parent0a3ac5ffeeec2bfd6a130d9082aa4ab5c5ca7fef [diff]
device/config: add raptor lake SOC to SOC list

BUG=b:302708504
TEST=./generate.sh

Change-Id: I19a10f98eab3e920337f6f1f8ecc5dec0858bc50
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/4916212
Reviewed-by: Jack Neus <jackneus@google.com>
Reviewed-by: Andrew Lamb <andrewlamb@chromium.org>
Commit-Queue: YH Lin <yueherngl@chromium.org>
3 files changed
tree: da36d6353cbcc28295593c13ecd1c2a30944047b
  1. extern/
  2. gen/
  3. go/
  4. infra/
  5. recipes/
  6. src/
  7. .gitattributes
  8. .gitignore
  9. buf.yaml
  10. generate.sh
  11. LICENSE
  12. OWNERS
  13. PRESUBMIT.cfg
  14. PRESUBMIT.py
  15. README.md
  16. setup_cipd.sh
  17. unblocked_terms.txt
README.md

infra/proto

infra/proto vs chromite/infra/proto

This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.

When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.