linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: arm-soc <arm@kernel.org>,
	linux-actions@lists.infradead.org,
	"Andreas Färber" <afaerber@suse.de>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] Actions ARM64 DT updates for v5.1
Date: Wed, 20 Feb 2019 16:37:58 +0100	[thread overview]
Message-ID: <CAK8P3a1k22OQF0iX8SR5RVS_9gfyYb19b9deuN_mNG+WF0LNGg@mail.gmail.com> (raw)
In-Reply-To: <20190218135042.GA13218@mani>

On Mon, Feb 18, 2019 at 2:50 PM Manivannan Sadhasivam
<manivannan.sadhasivam@linaro.org> wrote:
> ---
> The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
>
>   Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
>
> are available in the Git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/mani/linux-actions.git tags/actions-arm64-dt-for-v5.1
>
> for you to fetch changes up to 9175a8116f452a515cea734c6fedee6788e6bc33:
>
>   arm64: dts: actions: s700-cubieboard7: Enable I2C0 and I2C1 (2019-02-16 11:32:46 +0530)
>
> ----------------------------------------------------------------
> Actions ARM64 DT changes for v5.1:
>
> - Add interrupt properties to S900 pinctrl node
> - Add Reset controller support for S700
> - Add Reset controller support for S900
> - Add pinctrl support for S700
> - Add I2C support for S700
> - Enable I2C0 and I2C1 for s700-cubieboard7
>
> ----------------------------------------------------------------
> Manivannan Sadhasivam (3):
>       arm64: dts: actions: Add interrupt properties to pinctrl node for S900
>       arm64: dts: actions: Add Reset Controller support for S700 SoC
>       arm64: dts: actions: Add Reset Controller support for S900 SoC
>
> Parthiban Nallathambi (2):
>       arm64: dts: actions: s700: Add I2C controller nodes
>       arm64: dts: actions: s700-cubieboard7: Enable I2C0 and I2C1
>
> Saravanan Sekar (1):
>       arm64: dts: actions: Add pinctrl node for Actions Semi S700

Pulled into arm/dt, but please try to improve the tag description for
the next round: the text you have is more or less just a repeat
of the one-line subjects of the individual patches.

Instead, what you want to do is give a high-level description of what
is going on overall in your branch (e.g. adding multiple DT nodes for
missing devices) and ideally some background (e.g. how much
of the SoCs are actually described now, and how much is still
missing here).

       Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-02-20 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 13:50 [GIT PULL] Actions ARM64 DT updates for v5.1 Manivannan Sadhasivam
2019-02-18 16:49 ` Andreas Färber
2019-02-20 15:37 ` Arnd Bergmann [this message]
2019-02-21  9:33   ` Manivannan Sadhasivam

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=CAK8P3a1k22OQF0iX8SR5RVS_9gfyYb19b9deuN_mNG+WF0LNGg@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=afaerber@suse.de \
    --cc=arm@kernel.org \
    --cc=linux-actions@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=manivannan.sadhasivam@linaro.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;
as well as URLs for NNTP newsgroup(s).