Suggested-by: Frank Rowand <[email protected]> Signed-off-by: Jonathan Corbet <[email protected]> --- Documentation/SubmittingPatches | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index e6cbe59d890f..1f4e8c8710a7 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -15,7 +15,8 @@ format. For detailed information on how the kernel development process works, see Documentation/development-process. Also, read Documentation/SubmitChecklist for a list of items to check before submitting code. If you are submitting a driver, also read -Documentation/SubmittingDrivers. +Documentation/SubmittingDrivers; for device tree binding patches, read +Documentation/devicetree/bindings/submitting-patches.txt. Many of these steps describe the default behavior of the git version control system; if you use git to prepare your patches, you'll find much -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
