The first patch request

It was a little relaxing yesterday and Saturday. There was nothing to write about yesterday after watching Apsara in the evening.

When I went to work in the morning, I changed the charging implementation, that is, I added a reg_read to a register in reg_write to judge the data in this register, determine whether to perform this write operation based on the current status of the register. It's easy. I fixed a bug and came back.

Relax for one afternoon and look at driver_core's git repo at night. Then I changed the format of a function definition column with more than 80 columns, and thought I should learn how to send the patch. For the first time, I had to learn it slowly and read some git manual, it was found that git was a little powerful. It was just over 1 o'clock last night and there was no time to summarize it. Let's sum up today. I may look back at this for many years. I think it's silly, and there may be a lot of errors, but the first step is always beautiful.

Changed twice and used git commit twice.

Then git format-patch-2 and two patches are created.

Then, use git send-email to send it out. Several modules of Perl must be installed during the sending process.

 
Git format-patch-2-s -- To = wanlong.gao@gmail.com -- cc = lengyuex@gmail.com
 

Two patches are created.

VI ~ /. Gitconfig

 
[User] Name = Wanlong Gao email = wanlong.gao@gmail.com [sendemail] smtpencryption = TLS smtpserver = smtp.gmail.com smtpuser = wanlong.gao@gmail.com smtpserverport = 587
 

 
The email address and server are configured here.
 

Run the send-Email manual command to install Perl.
 

 
# Cpin-I net: SMTP: SSL
 

This installation is a little troublesome.

 
Git send-Email 0001-fixed-the-format-of-column-longer-than-80.patch
 

Send the patch, haha. I sent it to Greg, but it was busy. If it wasn't for a bird, it didn't make sense. It's good to learn how to send it, haha.

You can fix the bug and send a patch later. Haha. Powerful, powerful.

I was very excited last night.