From: Rask Ingemann Lambertsen <rask@formelder.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] ARM: dts: sun9i: Add mmc1 pinmux setting
Date: Fri, 24 Feb 2017 18:15:31 +0100 [thread overview]
Message-ID: <20170224171531.de4xghtzuffskucw@localhost> (raw)
In-Reply-To: <CAGb2v64Fw=NrBiFjkPbrWzyV-C1YFnp-=JmOo8zi8bnuHd29XA@mail.gmail.com>
On Fri, Feb 24, 2017 at 03:27:11PM +0800, Chen-Yu Tsai wrote:
> On Fri, Feb 24, 2017 at 2:08 PM, Chen-Yu Tsai <wens@csie.org> wrote:
> > commit 56b0730157f70dc23d6caff9e7ceb8b377b96b9f upstream.
> >
> > On the A80, mmc1 is available on pingroup G. Designs mostly use this
> > to connect to an SDIO WiFi chip.
> >
> > Signed-off-by: Chen-Yu Tsai <wens@csie.org>
>
> I did not send this.
>
> Rask, something is wrong with your setup. You should send patches from
> your own email address, while keeping the author. You should also add
> your SoB.
I'm terribly sorry about that. I am the one who sent that patch.
To prevent `git format-patch' from copying the commit author's address into
the From: field in the e-mail header again, I have now run
$ git config --global format.from true
so `git format-patch' will do the right thing. I wish that variable would be
more prominently documented, perhaps in git-format-patch(1).
--
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2017-02-24 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 6:07 [U-Boot] [PATCH 0/3] ARM: sun9i: Device tree and defconfig for Sunchip CX-A99 Rask Ingemann Lambertsen
2017-02-24 6:08 ` [U-Boot] [PATCH 1/3] ARM: dts: sun9i: Add mmc1 pinmux setting Chen-Yu Tsai
2017-02-24 7:27 ` Chen-Yu Tsai
2017-02-24 17:15 ` Rask Ingemann Lambertsen [this message]
2017-02-24 6:09 ` [U-Boot] [PATCH 2/3] ARM: dts: sun9i: Add device tree for Sunchip CX-A99 Rask Ingemann Lambertsen
2017-02-24 6:10 ` [U-Boot] [PATCH 3/3] ARM: sun9i: Add defconfig " Rask Ingemann Lambertsen
2017-02-24 17:42 ` [U-Boot] [PATCH 0/3] ARM: sun9i: Device tree and " Rask Ingemann Lambertsen
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=20170224171531.de4xghtzuffskucw@localhost \
--to=rask@formelder.dk \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.