From: Antonio Ospite <ao2@ao2.it>
To: AZO <typesylph@gmail.com>
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: input: joystick: Add PSX (Play Station 1/2) pad with SPI driver.
Date: Wed, 26 Apr 2017 10:52:24 +0200 [thread overview]
Message-ID: <20170426105224.3bfe4b9a2d9f07f58b22ac10@ao2.it> (raw)
In-Reply-To: <20170425144422.9179-1-typesylph@gmail.com>
On Tue, 25 Apr 2017 23:44:22 +0900
AZO <typesylph@gmail.com> wrote:
> PSX pads can be connected directry SPI bus.
^
"directly"
and add "to the" before SPI.
>
> Signed-off-by: AZO <typesylph@gmail.com>
> ---
Hi,
I haven't looked at the code but I have some general comments.
When submitting another iteration of a patch it's common practice to
mention the version in the Subject (e.g. [PATCH v3] ...), you can use:
git format-patch --subject-prefix='PATCH vX' ...
It is also useful to provide a changelog of the versions, so that
reviewers can see what the changes between the current patch and
the previous versions are. This changelog goes after the '---'
separator and before the diffstat, this way git will ignore it when the
patch is applied, it's meant for the review process and it doesn't need
to go in the commit message of the final version.
Further annotations can also go after the '---' separator.
For more details look at Documentation/SubmittingPatches in the linux
kernel tree.
Also try to use a subject line consistent with the subsystem, by
looking at the history of the files in the same directory.
In this case it could be something like:
Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver
Finally, script/checkpatch.pl suggests some minor issues, I tried with:
./scripts/checkpatch.pl --ignore LONG_LINE,LONG_LINE_COMMENT your.patch
You can ignore some of them, and motivate your decision in an
annotation.
Also try to comment when you do not agree with the reviewer or cannot
comply (for example about using an interrupt instead of polling).
It's fine if your English is not perfect yet, don't let that stop you :)
Ciao ciao,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
next prev parent reply other threads:[~2017-04-26 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 14:44 AZO
2017-04-26 8:52 ` Antonio Ospite [this message]
2017-04-26 11:46 ` AZO
2017-04-27 8:17 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2017-04-28 2:38 Tomohiro Yoshidomi
2017-04-25 7:41 AZO
2017-04-25 22:16 ` kbuild test robot
2017-04-25 22:24 ` kbuild test robot
2017-04-25 23:07 ` AZO
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170426105224.3bfe4b9a2d9f07f58b22ac10@ao2.it \
--to=ao2@ao2.it \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=typesylph@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®