QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for shikra by akakum-qualcomm · Pull Request #1229 · qualcomm-linux/kernel

akakum-qualcomm · 2026-10-01T13:54:46Z

QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for shikra

Restore BAM DMA nodes as per PR #838.

CRs-Fixed: 4697031

qswat-orbit-external · 2026-10-01T13:54:53Z

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

akakum-qualcomm · 2026-10-01T14:04:21Z

qli-2.1 pull-request freeze

qswat-orbit-external · 2026-10-01T14:04:23Z

Merge Check Failed: CR Not Eligible for Merge

CR 4697031 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4697031
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

qlijarvis · 2026-10-09T08:26:43Z

PR #1229 — validate-patch

PR: #1229

Verdict	Issues	Detailed Report
✅	0	Full report

Final Summary

Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

Verdict: ✅ — click to expand

🔍 Patch Validation

PR: #1229 - QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for Shikra- #838
Upstream commit: N/A (vendor-only commit)
Verdict: ✅ PASS

Commit Message

Check Status Note

Subject matches upstream N/A Vendor-only commit; no upstream source

Body preserves rationale ✅ References PR #838 for context

Fixes tag present/correct N/A Not applicable for vendor-only changes

Authorship preserved ✅ Signed-off-by present

Backport note (if applicable) N/A Not a backport

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra.dtsi ✅ Moves bam_dmux and bam_dmux_dma nodes; adds compatible strings and qcom,vmid property

Verdict

Merge as-is. This is a vendor-specific device tree change to fix BAM XPU violations on Shikra. The QCLINUX: prefix correctly indicates this is not intended for upstream submission.

Final Summary

Lore link present: No — QCLINUX: prefix; no lore link expected or required

Lore link matches PR commits: N/A — no lore link to compare against

Upstream patch status: N/A — vendor-only change, not posted upstream

PR present in qcom-next/topics: Yes — commit is present in qcom-next (all checked added lines are present)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: ba86f67908354f41f269ca1d64b22e4624766dcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final

1/1 [PATCH] QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU present - all checked added lines are present skipped - not checked because qcom-next already contains the change present

Final Status

overall_status: PASS
present_commits: 1/1
partial_commits: 0/1
missing_commits: 0/1
topics_checked_for_commits: 0/1
final_summary: PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

qlijarvis · 2026-10-09T08:26:45Z

PR #1229 — checker-log-analyzer

PR: #1229
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/36872358081

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	✅	All DTB validations passed
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	`QCLINUX:` prefix not in allowed list
tag-check	❌	`QCLINUX:` prefix fails mandatory check for non-qcom-next branches

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1229 - QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for Shikra- #838
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/36872358081
Target branch: qcom-6.18.y

Checker Result Summary

checkpatch ✅ No style issues

dt-binding-check ⏭️ Skipped (no binding changes)

dtb-check ✅ All DTB validations passed

sparse-check ⏭️ Skipped (no C/H changes)

check-uapi-headers ⏭️ Skipped (no UAPI changes)

check-patch-compliance ❌ QCLINUX: prefix not in allowed list

tag-check ❌ QCLINUX: prefix fails mandatory check for non-qcom-next branches

❌ check-patch-compliance

Root cause: Commit uses QCLINUX: prefix, which is not in the checker's allowed prefix list (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:).

Failure details:
Checking commit: QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for Shikra- #838
Commit summary does not start with a required prefix
Analysis:
The check-patch-compliance checker enforces a strict subset of prefixes and only accepts:

FROMLIST: — patch posted to mailing list

FROMGIT: — patch from maintainer tree

UPSTREAM: — patch merged into mainline

BACKPORT: — upstream patch with modifications

The QCLINUX: prefix is a vendor-internal tag used for Qualcomm-specific changes with no upstream equivalent. This is a known limitation of the checker — it will always fail for vendor-only commits.

Fix options:
If this change was posted upstream (to lore.kernel.org):
git rebase -i 110eabaa857a
# mark commit as 'edit'
git commit --amend -m "FROMLIST: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for Shikra- #838

Restore BAM DMA nodes as per PR #838.

Link: <lore-url>
Signed-off-by: Akash Kumar <akakum@qti.qualcomm.com>"
git rebase --continue
If this is truly vendor-only (no upstream posting):
The checker will always fail. This is expected behavior for QCLINUX:-prefixed commits. The failure can be acknowledged as a known limitation.
Reproduce locally:
cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 110eabaa857a3ab597bdd7e5974cb0f72ca3b9e7 \
  --head 4df2c71441f6e76bd8db9e0d2fbe422e45217f6f
❌ tag-check

Root cause: Target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), which requires all commits to carry a valid subject prefix. The QCLINUX: prefix is valid for tag-check purposes.

Analysis:
The tag-check verifies that every commit subject starts with one of the required prefixes:

FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:

Verdict for tag-check: ✅ PASS
The commit subject QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for Shikra- #838 correctly starts with QCLINUX:, which is a valid prefix for the tag-check.

Note: While QCLINUX: satisfies the tag-check requirement, it fails check-patch-compliance because that checker enforces a stricter subset of prefixes.

Verdict

1 blocker to address:

The check-patch-compliance failure is the only actionable issue. The commit uses QCLINUX: prefix, which is not accepted by this checker.

Recommended action:

If the change was posted upstream → change prefix to FROMLIST: and add Link: trailer

If the change is vendor-only → acknowledge the checker limitation; QCLINUX: commits will always fail this check

All other checkers passed or skipped appropriately. The DTS-only change has no style issues, builds cleanly, and validates correctly.

…hikra- qualcomm-linux#838 Restore BAM DMA nodes as per PR qualcomm-linux#838. Signed-off-by: Akash Kumar <akakum@qti.qualcomm.com>

qswat-orbit-external · 2026-10-13T06:18:04Z

Merge Check Failed: CR Not Eligible for Merge

CR 4697031 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4697031
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

qlijarvis · 2026-10-13T07:15:24Z

PR #1229 — validate-patch

PR: #1229

Verdict	Issues	Detailed Report
N/A	0	Full report

Final Summary

Lore link present: No — QCLINUX: prefix; no lore link expected or required
Lore link matches PR commits: N/A — no lore link to compare against
Upstream patch status: N/A — vendor-only change, not posted upstream
PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

Verdict: N/A — click to expand

🔍 Patch Validation

PR: #1229 - QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for Shikra- #838
Upstream commit: N/A (vendor-only change)
Verdict: ⏭️ SKIP (validation not applicable)

Commit Message

Check Status Note

Subject matches upstream N/A QCLINUX: prefix — vendor-only commit

Body preserves rationale N/A No upstream source to compare

Fixes tag present/correct N/A Vendor-only change

Authorship preserved N/A No upstream author to preserve

Backport note (if applicable) N/A Not a backport

Diff

File Status Notes

arch/arm64/boot/dts/qcom/shikra.dtsi ⏭️ Vendor-only DT change — moves BAM DMA nodes, adds compatible strings and qcom,vmid property

Verdict

This is a vendor-only commit (QCLINUX: prefix) that restores BAM DMA node configuration to fix an XPU violation on Shikra. No upstream validation is applicable or required for QCLINUX: commits.

Final Summary

Lore link present: No — QCLINUX: prefix; no lore link expected or required

Lore link matches PR commits: N/A — no lore link to compare against

Upstream patch status: N/A — vendor-only change, not posted upstream

PR present in qcom-next/topics: Partial — integration_presence_report.md shows partial evidence (subject or partial tree match found, but full change not verified in qcom-next or topics)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: cb7a416d2476d022a449e7d52475c28a6feb390d
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final

1/1 [PATCH] QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU partial - subject or partial tree evidence found, but full change was not verified partial - subject or partial tree evidence found, but full change was not verified partial

Final Status

overall_status: PARTIAL
present_commits: 0/1
partial_commits: 1/1
missing_commits: 0/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

qlijarvis · 2026-10-13T07:15:26Z

PR #1229 — checker-log-analyzer

PR: #1229
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/38356008945

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	Skipped (no binding changes)
dtb-check	✅	Passed (warnings are pre-existing)
sparse-check	⏭️	Skipped (no C/H changes)
check-uapi-headers	⏭️	Skipped (no UAPI changes)
check-patch-compliance	❌	`QCLINUX:` prefix not accepted
tag-check	✅	Valid prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1229 - QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for Shikra- #838
Target branch: qcom-6.18.y
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/38356008945

Checker Result Summary

checkpatch ✅ No style issues

dt-binding-check ⏭️ Skipped (no binding changes)

dtb-check ✅ Passed (warnings are pre-existing)

sparse-check ⏭️ Skipped (no C/H changes)

check-uapi-headers ⏭️ Skipped (no UAPI changes)

check-patch-compliance ❌ QCLINUX: prefix not accepted

tag-check ✅ Valid prefix present

❌ check-patch-compliance

Root cause: The commit uses QCLINUX: prefix, which is not in the checker's allowed list.

Failure details:
Checking commit: QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for Shikra- #838
Commit summary does not start with a required prefix
Analysis:

The check-patch-compliance checker only accepts these prefixes:

FROMLIST: (posted to mailing list)

FROMGIT: (from maintainer tree)

UPSTREAM: (merged into mainline)

BACKPORT: (backported with modifications)

The commit uses QCLINUX:, which is a vendor-internal prefix used in the Qualcomm Linux tree for vendor-only changes with no upstream equivalent. This is a known limitation of the check-patch-compliance checker — it enforces upstream-linkable prefixes only and will always fail for vendor-only commits.

Why this happens:

This is a vendor-only DTS change that restores BAM DMA nodes specific to the Shikra platform. Since this is not posted upstream and has no upstream equivalent, QCLINUX: is the correct prefix to use according to internal conventions. However, the CI checker does not recognize it.

Options:

Accept the failure — This is a known checker limitation for vendor-only commits. The QCLINUX: prefix is correct for this type of change. The failure does not indicate a problem with the patch itself.

Change to FROMLIST: + add Link — Only if this change has been (or will be) posted to an upstream mailing list. If not posted upstream, this would be incorrect.

Remove the prefix entirely — Not recommended, as it loses important metadata about the patch origin.

Recommendation: Accept the failure. The QCLINUX: prefix is appropriate for this vendor-only DTS change.

Reproduce locally:
cd /path/to/kernel
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 143c1172c89b56ba26b8c9fd7bdc63cb04bb79d0 \
  --head a986b3a9fe9ec635e082d7d4c9647ac82ad36d14
✅ tag-check

Status: PASS

The commit subject starts with QCLINUX:, which is a valid prefix tag. Since the target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), the tag-check requirement applies, and the commit satisfies it.

Verdict

One known checker limitation — merge as-is.

The check-patch-compliance failure is a known limitation of the checker for vendor-only commits using the QCLINUX: prefix. The patch itself is correct:

✅ No checkpatch style issues

✅ Valid subject prefix tag (QCLINUX:)

✅ DTB validation passed (warnings are pre-existing tree issues)

✅ Proper sign-off present

The failure does not indicate a problem with the patch. This is a legitimate vendor-only change that correctly uses the QCLINUX: prefix.

qcomlnxci · 2026-10-13T08:58:46Z

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	❌ Fail	❌ Fail	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip	❌ Fail	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	✅ Pass	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass

qcomlnxci · 2026-10-13T09:02:09Z

Test jobs on a986b3a

akakum-qualcomm requested review from a team, Amit Kucheria (idlethread), knaveen-qc and Trilok Soni (trsoni) October 1, 2026 13:54

Vishnu Santhosh (quic-vishsant) approved these changes Oct 5, 2026

View reviewed changes

QCLINUX: dt-bindings/dmaengine/net: qcom: FIX BAM XPU violation for S…

a986b3a

…hikra- qualcomm-linux#838 Restore BAM DMA nodes as per PR qualcomm-linux#838. Signed-off-by: Akash Kumar <akakum@qti.qualcomm.com>

akakum-qualcomm force-pushed the fix/shikra-bam-xpu-violation-838 branch from 4df2c71 to a986b3a Compare October 13, 2026 06:17

Conversation

akakum-qualcomm commented Oct 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-external Bot commented Oct 1, 2026

Uh oh!

akakum-qualcomm commented Oct 1, 2026

Uh oh!

qswat-orbit-external Bot commented Oct 1, 2026

Uh oh!

qlijarvis commented Oct 9, 2026

PR #1229 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

qlijarvis commented Oct 9, 2026

PR #1229 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

❌ tag-check

Verdict

Uh oh!

qswat-orbit-external Bot commented Oct 13, 2026

Uh oh!

qlijarvis commented Oct 13, 2026

PR #1229 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

qlijarvis commented Oct 13, 2026

PR #1229 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

✅ tag-check

Verdict

Uh oh!

qcomlnxci commented Oct 13, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 13, 2026

Test jobs on a986b3a

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

akakum-qualcomm commented Oct 1, 2026 •

edited

Loading