[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57513DD5.3060507@metafoo.de>
Date: Fri, 3 Jun 2016 10:20:37 +0200
From: Lars-Peter Clausen <lars@...afoo.de>
To: Rocky Hsiao <rocky.hsiao@...a-image.com>,
linux-kernel@...r.kernel.org
Cc: Jonathan Cameron <jic23@...nel.org>,
Hartmut Knaack <knaack.h@....de>,
Peter Meerwald <pmeerw@...erw.net>,
Olof Johansson <olofj@...omium.org>,
Filipe Brandenburger <filbranden@...omium.org>,
Brian Norris <briannorris@...omium.org>,
Benson Leung <bleung@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Sonny Rao <sonnyrao@...omium.org>,
Daniel Kurtz <djkurtz@...omium.org>,
Daniel Baluta <daniel.baluta@...el.com>,
Adriana Reus <adriana.reus@...el.com>,
Gwendal Grignou <gwendal@...omium.org>,
Matt Ranostay <mranostay@...il.com>,
Puthikorn Voravootivat <puthik@...omium.org>,
Andreas Dannenberg <dannenberg@...com>,
linux-iio@...r.kernel.org, John Huang <john.huang@...a-image.com>
Subject: Re: [PATCH] Dyna-Image AL3320A update, add AL3010 driver
On 06/03/2016 06:02 AM, Rocky Hsiao wrote:
> 1. Change al3320a.c to match light sensor test flow.
> 2. Add al3010.c to add new device AL3010.
> original file copy from al3320a.c
Hi,
Thanks for the patch. In addition to what Daniel said, for upstream patch
submissions it is important to have proper commit messages explaining what
is done, why it is done and how it is done. The commit messages should
follow the general style of the subsystem you are sending the patch to. E.g.
in the IIO case this means that the subject line should start with "iio: ...".
http://chris.beams.io/posts/git-commit/ is a very good document that
describes how to create a good commit message and I recommend reading it.
- Lars
Powered by blists - more mailing lists