From: Maxime Ripard <maxime@cerno.tech>
To: Alexandre GRIVEAUX <agriveaux@deutnet.info>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, wens@csie.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: sun5i: Add dts for inet86v_rev2
Date: Fri, 14 Feb 2020 14:17:41 +0100 [thread overview]
Message-ID: <20200214131741.u46urhpwzzjpflfb@gilmour.lan> (raw)
In-Reply-To: <864838c2-1b1d-433a-ca04-0d91c8b5b8ca@deutnet.info>
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
Hi,
On Wed, Feb 12, 2020 at 10:45:03AM +0100, Alexandre GRIVEAUX wrote:
> Le 11/02/2020 à 14:15, Maxime Ripard a écrit :
> > On Mon, Feb 10, 2020 at 11:35:52AM +0100, agriveaux@deutnet.info wrote:
> >> From: Alexandre GRIVEAUX <agriveaux@deutnet.info>
> >>
> >> Add Inet 86V Rev 2 support, based upon Inet 86VS.
> >>
> >> Missing things:
> >> - Accelerometer (MXC6225X)
> >> - Touchpanel (Sitronix SL1536)
> >> - Nand (29F32G08CBACA)
> >> - Camera (HCWY0308)
> >>
> >> Signed-off-by: Alexandre GRIVEAUX <agriveaux@deutnet.info>
> > Please read the documentation I sent you yesterday. In particular,
> > when submitting multiple versions, you should remove have the version
> > number in the title and a changelog.
> >
> > Also, please ask questions if you're unsure about something, or
> > discuss something you do not agree with instead of ignoring the
> > comment.
> >
> > Maxime
>
>
> Seem I misusing 'git send-email' because i already changed the subject
> line (same apply to u-boot):
>
> git send-email --from agriveaux@deutnet.info --to
> robh+dt@kernel.org,mark.rutland@arm.com,mripard@kernel.org,wens@csie.org
> --cc
> linux-kernel@vger.kernel.org,devicetree@vger.kernel.org,agriveaux@deutnet.info
> --subject '[v2] ARM: dts: sun5i: Add dts for inet86v_rev2' --compose
> /tmp/linux/0001-ARM-dts-sun5i-Add-dts-for-inet86v_rev2.patch
>
> It's the first time i use git send-email, previously i used mutt to send
> patchsets (on mips mostly).
>
>
> Effectively i've forgot the changelog...
A simpler way, especially for a single patch, would be to use
git send-email -v2 --to $recipients --annotate $COMMIT^..$COMMIT
You can even keep the change log in the commit log itself by using ---
as a separator, so something like:
ARM: dts: my super title
Some nice awesome change
---
Changes from v1:
- Whatever.
> At why do we need another device tree:
>
> inet86vs use a GSL1680 touchpanel controller and 4GB nand [0]
>
> inet86vsuse a Sitonix SL1536 touchpanel controller and 8GB nand (can
> have 16GB nand)[1]
NAND size will be discovered so it's not really a concern. For the
touchscreen, you should make that clear in your commit log.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-02-14 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 10:35 agriveaux
2020-02-11 13:15 ` Maxime Ripard
2020-02-12 9:45 ` Alexandre GRIVEAUX
2020-02-14 13:17 ` Maxime Ripard [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-10 9:27 agriveaux
2020-02-10 9:27 ` [PATCH] " agriveaux
2020-02-10 9:41 ` Maxime Ripard
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=20200214131741.u46urhpwzzjpflfb@gilmour.lan \
--to=maxime@cerno.tech \
--cc=agriveaux@deutnet.info \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®