-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Closed
Labels
BackportBackport PR and backport failure issuesBackport PR and backport failure issues
Description
This issue was created automatically because the backport of #77209 to v3.7-branch failed.
The backport to v3.7-branch failed:
Auto-merging drivers/rtc/rtc_rv3028.c
[backport-77209-to-v3.7-branch a53176eeeca] drivers: rtc: rv3028: fix minutes alarm
Author: Jakub Topic <[email protected]>
Date: Sun Aug 18 20:32:18 2024 +0200
1 file changed, 3 insertions(+), 3 deletions(-)
Auto-merging drivers/rtc/rtc_rv3028.c
CONFLICT (content): Merge conflict in drivers/rtc/rtc_rv3028.c
error: could not apply b824e41bf39... drivers: rtc: rv3028: adjust timing of EEPROM requests
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"
To backport manually, run these commands in your terminal:
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v3.7-branch v3.7-branch
# Navigate to the new working tree
cd .worktrees/backport-v3.7-branch
# Create a new branch
git switch --create backport-77209-to-v3.7-branch
# Cherry-pick the merged commits of this pull request and resolve the conflicts
git cherry-pick -x b824e41bf3921ee75143c2d0b85e009372cb5698~2..b824e41bf3921ee75143c2d0b85e009372cb5698
# Push it to GitHub
git push --set-upstream origin backport-77209-to-v3.7-branch
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v3.7-branchThen, create a pull request where the base branch is v3.7-branch and the compare/head branch is backport-77209-to-v3.7-branch.
Metadata
Metadata
Assignees
Labels
BackportBackport PR and backport failure issuesBackport PR and backport failure issues