From: martinayotte@gmail.com (martinayotte at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/1] add missing UARTs pins and I2C entriesfor AllWinner H3 DTSI
Date: Wed, 4 May 2016 11:15:55 -0700 (PDT) [thread overview]
Message-ID: <c17544c6-2b49-44cc-b2f9-537d94f276ef@googlegroups.com> (raw)
In-Reply-To: <20160502064645.GK17159@lukather>
Bonjour Maxime,
On Monday, May 2, 2016 at 2:46:57 AM UTC-4, Maxime Ripard wrote:
> Hi,
>
> On Tue, Apr 19, 2016 at 03:50:39PM -0400, Martin Ayotte wrote:
> > Hi everyone,
> >
> > This patch is submit to provide endusers access to additional UARTs on
> > AllWinner H3 SoC along with I2C ports.
>
> Unfortunately, your patch cannot be applied in its current form, both
> because of process and technical reasons:
>
> * Every commits should have a commit title and log. While you do
> have a title, you used the log to store your cover letter. This is
> an issue, because that will be kept in the git history, which is
> obviously something we don't want.
> If you want to make a cover letter, you can either send it as a
> separate mail, or after the "---" below that will be ignored when
> applying the mails.
> On the other hand, the commit log should be used to say why ?our
> doing this patch and why it was needed.
>
> * You do not have a Signed-off-by tag in your commit log. This and
> the point above is documented in Documentation/SubmittingPatches,
> please make sure to read that first.
>
> * Your mailer completely corrupted the patch when you sent it,
> replacing all tabs by spaces, and wrapping the longer lines. That
> means that the patch cannot be applied anymore. Please fix your
> mailer, or use one that just works, like git send-email.
>
> * Finally, like Chen-Yu already told you, you're doing several
> different things here in a single patch, while you should have
> done separate patches. From what I can see, you're adding pinctrl
> groups for the uart and i2c pins, and adding the i2c controller
> nodes. That should have been ideally 3 patches: 1 for the uart
> pinctrl groups, 1 for the i2c pinctrl groups, 1 for the i2c
> controller nodes. We also don't take pinctrl groups that are not
> enabled on any boards to keep the DT size as small as possible.
>
> Thanks,
> Maxime
>
> --
> Maxime Ripard, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
Thanks for your help and make me understanding more the process.
I've now prepared a new v3 for that, and just send it.
Strangely, it seems that the 3 patches been sent separately.
I will try to figure out what happened.
Regards,
Martin.
prev parent reply other threads:[~2016-05-04 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 19:50 [PATCH v2 1/1] add missing UARTs pins and I2C entriesfor AllWinner H3 DTSI Martin Ayotte
2016-05-02 6:46 ` Maxime Ripard
2016-05-04 18:15 ` martinayotte at gmail.com [this message]
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=c17544c6-2b49-44cc-b2f9-537d94f276ef@googlegroups.com \
--to=martinayotte@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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