Repository Workflow: //////////////////// Here are some guidelines for users or developers regarding the work with this Git repository. * Users: - steps to verify a release tag can be done with GPG: git show maint-dborkman-pgp-pub | gpg --import git show maint-tklauser-pgp-pub | gpg --import git tag -v * Developers: - steps to submit a patch: we follow in general a similar submission process as in the Linux kernel read https://www.kernel.org/doc/Documentation/SubmittingPatches read Documentation/SubmittingPatches if a commit was acknowledged by someone, add Acked-by: Random J Developer if a bug was reported by someone, add Reported-by: Random J Developer if a feature was suggested by someone, add Suggested-by: Random J Developer if a commit was tested by someone, add Tested-by: Random J Developer if a commit was reviewed by someone, add Reviewed-by: Random J Developer if a bug was bisected by someone, add Bisected-by: Random J Developer in case tagging as mentioned above already happened internally in your company by different persons, you can add those tags before submission into the patch commit message in case someone on the mailing list adds his/her *-by tag, it's the job of the maintainer to keep track of that and to apply this properly * Maintainer: - steps to add your public GPG key: gpg --gen-key [...] gpg --list-keys [take the pubkey id you want to add] gpg -a --export | git hash-object -w --stdin git tag -a maint--pgp-pub .> git push --tags - steps to make a new release: set proper versioning in the Makefile itself make release git push --tags upload tarballs to public dir update website email generated .MAIL_MSG to the mailing list, include bcc to the maintainers listed in Documentation/Downstream - apply patches from non-maintainers, basic rules to follow: preferred are patches that have been sent via git send-email never do an automatic Github merge in case the pull request came from there in case of Github we need to do cherry-picking if it's a pull request, make sure it does not contain merges itself always add your Signed-off-by to the commit message in case of an apply patches must be rejected in case the developer's Signed-off-by is missing name='qt'>
path: root/Documentation/i2c
diff options
context:
space:
mode:
authorPhil Reid <preid@electromag.com.au>2016-08-31 15:31:38 +0800
committerMark Brown <broonie@kernel.org>2016-09-01 20:53:31 +0100
commitf99008013e199e6b88ef26c98ecb042c94c7450c (patch)
tree8d06d437619946dcdb853cae1e1af7f80a468596 /Documentation/i2c
parent29b4817d4018df78086157ea3a55c1d9424a7cfc (diff)
spi: sc18is602: Add reset control via gpio pin.
This sc18is602 has a reset pin that may need to be deasserted. Add optional binding to specifiy the reset pin via a gpio and deassert during probe. Signed-off-by: Phil Reid <preid@electromag.com.au> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'Documentation/i2c')