On Tue, Mar 22, 2022 at 09:54:08PM +0800, Sui Jingfeng wrote: > > On 2022/3/22 21:08, Jiaxun Yang wrote: > > > > > > 在 2022/3/22 2:33, Sui Jingfeng 写道: > > > > > > On 2022/3/22 07:20, Rob Herring wrote: > > > > On Tue, Mar 22, 2022 at 12:29:14AM +0800, Sui Jingfeng wrote: > > > > > From: suijingfeng <suijingfeng@xxxxxxxxxxx> > > > > > > > > > Needs a commit message. > > > > > > > > > Signed-off-by: suijingfeng <suijingfeng@xxxxxxxxxxx> > > > > > Signed-off-by: Sui Jingfeng <15330273260@xxxxxx> > > > > Same person? Don't need both emails. > > > > > > Yes, suijingfeng@xxxxxxxxxxx is my company's email. But it can not > > > be used to send patches to dri-devel, > > > > > > when send patches with this email, the patch will not be shown on > > > patch works. > > > > > > Emails are either blocked or got rejected by loongson's mail > > > server. It can only receive emails > > > > > > from you and other people, but not dri-devel. so have to use my > > > personal email(15330273260@xxxxxx) to send patches. > > In this case you can just use your company's email to sign-off > > code and sending with your personal email. It's common practice. > > > > If you don't want to receiving kernel email in your company mailbox, > > you can add a entry in .mailmap . > > > |I'm using `git send-email -7 --cover-letter --annotate -v11` command to > send patches, it will automatically sign off patches with the my private > emails. | I think that is only if you set your git config author to your private email. Pretty much anything git might automatically do can be turned off. Rob
