-
Notifications
You must be signed in to change notification settings - Fork 5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
pinctrl-bcm2835: bcm2835_gpio_direction_output must set the value
- Loading branch information
Phil Elwell
committed
Feb 4, 2015
1 parent
bac69e3
commit c288c0e
Showing
1 changed file
with
8 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c288c0e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @pelwell , I used a workaround for this in an Intel 8080 bus driver that I started to work on (was put on hold when FBTFT entered staging).
Please send it upstream as well.
c288c0e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have any hints on how to go about that?
c288c0e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have e-mail set up on my Linux machine, so I had to set my smtp server like this:
I also had to change user.name to my full name, because I used 'notro' before and it messed up an email header (I don't remember exactly how).
You need to expand a bit on that commit message. A heading and description is required:
Maybe something like this:
Then I prepared the last commit I had made:
You can use '-o' to put the patches somewhere else.
Who should receive it:
From this I would send it to:
To: linus.walleij@linaro.org
Cc: swarren@wwwdotorg.org
Cc: lee@kernel.org
Cc: linux-gpio@vger.kernel.org
Cc: linux-rpi-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Then finally send the patch:
Try sending it to yourself first to make sure everything is fine.
I've only sent 3 patches myself, so this is surely only a hint :-)
Refs:
http://kernelnewbies.org/PatchPhilosophy
https://burzalodowa.wordpress.com/2013/10/05/how-to-send-patches-with-git-send-email/
https://www.kernel.org/doc/Documentation/SubmittingPatches
c288c0e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Brilliant. Thanks - I'll see how I get on.