[roll] Roll fuchsia [assembly][fshost] Add a board provided feature for inline_crypto

In production, inline encryption and barrier usage will be 1:1. That is,
barriers will be enabled iff inline encryption is enabled. However,
tests will be able to enable barriers without inline crypto via
FilesystemOptions.

See go/fxfs-barriers for more context on barriers.

Original-Bug: b/393448861
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1260725
Original-Revision: 379bbf05b94af1dbfa93cf3478e567615e056a40
GitOrigin-RevId: 8c5d75aa3729e0cc8b7755b0dbc810cc5e728c78
Change-Id: I9fbe4d8b149018851badd857a40b2859dd9ed72d
1 file changed
tree: c21b7bac430314b0188658b6884a8f602a172c16
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.