1. 19 Apr, 2021 3 commits
    • Chris Kay's avatar
      build(hooks): add Commitizen hook · c75ce067
      Chris Kay authored
      
      
      This change adds Commitizen, an interactive tool for writing commit
      messages, to the package.json file. This installs Commitizen within the
      `node_modules` directory automatically when developers invoke
      `npm install` from the root repository directory.
      
      Additionally, this change adds a prepare-commit-msg Git hook which
      invokes Commitizen prior to generation of the default commit message.
      It may be exited with the standard ^C signal without terminating the
      commit process for those who desperately want to avoid using it, but
      otherwise should encourage developers to conform to the new commit style
      without running into post-commit linting errors.
      
      Change-Id: I8a1e268ed40b61af38519d13d62b116fce76a494
      Signed-off-by: default avatarChris Kay <chris.kay@arm.com>
      c75ce067
    • Chris Kay's avatar
      build(hooks): add Gerrit hook · 4b7eee81
      Chris Kay authored
      
      
      This change adds the Gerrit commit-msg hook to Husky, such that it now
      no longer requires manual installation by the developer.
      
      This hook was pulled directly from the TF-A Gerrit review server.
      
      Change-Id: I79c9b0ce78fd326fda6db7a930b7277690177f28
      Signed-off-by: default avatarChris Kay <chris.kay@arm.com>
      4b7eee81
    • Chris Kay's avatar
      build(hooks): add Husky configuration · ba39362f
      Chris Kay authored
      
      
      Husky is a tool for managing Git hooks within the repository itself.
      Traditionally, commit hooks need to be manually installed on a per-user
      basis, but Husky allows us to install these hooks either automatically
      when `npm install` is invoked within the repository, or manually with
      `npx husky install`.
      
      This will become useful for us in the next few patches when we begin
      introducing tools for enforcing a commit message style.
      
      Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830
      Signed-off-by: default avatarChris Kay <chris.kay@arm.com>
      ba39362f
  2. 16 Apr, 2021 1 commit
  3. 15 Apr, 2021 1 commit
  4. 14 Apr, 2021 3 commits
  5. 13 Apr, 2021 2 commits
  6. 12 Apr, 2021 4 commits
  7. 09 Apr, 2021 1 commit
    • Manish Pandey's avatar
      plat/arm: don't provide NT_FW_CONFIG when booting hafnium · 2b6fc535
      Manish Pandey authored
      
      
      NT_FW_CONFIG file is meant to be passed from BL31 to be consumed by
      BL33, fvp platforms use this to pass measured boot configuration and
      the x0 register is used to pass the base address of it.
      
      In case of hafnium used as hypervisor in normal world, hypervisor
      manifest is expected to be passed from BL31 and its base address is
      passed in x0 register.
      
      As only one of NT_FW_CONFIG or hypervisor manifest base address can be
      passed in x0 register and also measured boot is not required for SPM so
      disable passing NT_FW_CONFIG.
      Signed-off-by: default avatarManish Pandey <manish.pandey2@arm.com>
      Change-Id: Ifad9d3658f55ba7d70f468a88997d5272339e53e
      2b6fc535
  8. 08 Apr, 2021 9 commits
  9. 07 Apr, 2021 7 commits
  10. 06 Apr, 2021 7 commits
  11. 01 Apr, 2021 2 commits