From: "Arnd Bergmann" <arnd@arndb.de>
To: "gordon.ge" <gordon.ge@bst.ai>, soc@lists.linux.dev
Cc: "yangzh0906@thundersoft.com" <yangzh0906@thundersoft.com>,
linux-arm-kernel@lists.infradead.org,
bst-upstream <bst-upstream@bstai.top>
Subject: Re: [GIT PULL]arm64: BST C1200 eMMC DTS for v7.2
Date: Thu, 11 Jun 2026 15:44:55 +0200 [thread overview]
Message-ID: <c7aa4a27-d523-4c83-8a5b-d2e7998d7e97@app.fastmail.com> (raw)
In-Reply-To: <20260611.111859-gordon.ge@bst.ai>
On Thu, Jun 11, 2026, at 05:21, gordon.ge@bst.ai wrote:
>
> Thank you for the review.
> I have fixed the two issues you mentioned and updated the pull request.
Hi Gordon,
unfortunately, I'm still seeing new problems here:
- you use a git@github.com url, which I can't pull from. Please
add an 'insteadOf' rule to your .gitconfig that rewrites this
to an https:// style address (or edit the text manually)
- https://patchwork.kernel.org/project/linux-soc/list/ does not
actually show the contents of your pull requests. This is
probably not caused by something you did, but it may be
related to the URL problem.
- The commit you have contains
Author: Gordon Ge <gordon.ge@bst.ai>
Commit: Gordon Ge <gordon.ge@bst.ai>
Signed-off-by: Albert Yang <yangzh0906@thundersoft.com>
Acked-by: Gordon Ge <gordon.ge@bst.ai>
which is not correct. If you commit the patch, your own
Signed-off-by needs to be included, see
https://www.kernel.org/pub/software/scm/git/docs/SubmittingPatches.html
If Albert was the original author, you should also reflect
that by using 'git commit --author="Albert Yang <yangzh0906@thundersoft.com>"'
Since we are getting very close to the merge window, I can't
guarantee that the patches make it in, but please resend
anyway. It may be easier to send these as individual
patches instead of pull requests, but that is up to you.
Arnd
prev parent reply other threads:[~2026-06-11 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 3:21 [GIT PULL]arm64: BST C1200 eMMC DTS for v7.2 gordon.ge
2026-06-11 13:44 ` Arnd Bergmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c7aa4a27-d523-4c83-8a5b-d2e7998d7e97@app.fastmail.com \
--to=arnd@arndb.de \
--cc=bst-upstream@bstai.top \
--cc=gordon.ge@bst.ai \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@lists.linux.dev \
--cc=yangzh0906@thundersoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox