From: Jisheng.Zhang@synaptics.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] berlin dt64 changes for v4.20
Date: Sat, 29 Sep 2018 09:33:26 +0800 [thread overview]
Message-ID: <20180929093309.08c32dca@xhacker.debian> (raw)
In-Reply-To: <CAK8P3a3T=P1SS9DRSNEniBrOkKJhd__FoMGZZ_Kt6Xjd32NXGA@mail.gmail.com>
On Fri, 28 Sep 2018 12:40:43 +0200 Arnd Bergmann wrote:
> On Thu, Sep 27, 2018 at 10:24 AM Jisheng Zhang
> <Jisheng.Zhang@synaptics.com> wrote:
> >
> >
> > The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
> >
> > Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jszhang/linux-berlin.git tags/berlin64-dt-for-v4.20
> >
> > for you to fetch changes up to 087682f5a75bec349cdcb34c29384a051587aa99:
> >
> > arm64: dts: synaptics: add dtsi file for Synaptics AS370 SoC (2018-09-27 14:48:43 +0800)
> >
> > ----------------------------------------------------------------
> > Berlin64 DT changes for v4.20
> >
> > - move berlin binding documentation to syna.txt
> > - add binding for the AS370 SoC
> > - add dtsi file for Synaptics AS370 SoC
>
> Pulled into next/dt, but I noticed that the tag description was different on
> the signed tag compared to the one in the email. I left it with the
> one-line version, since the bullet list you have here does not add
> any information that is not already part of the one-line patch
> descriptions below it.
>
> It would be nice to get a real description of the series as a whole
> in the signed tag instead, to explain what overall theme is. In
> this case, a good text would explain what the 'AS370 SoC' is,
> including its main features and when this is expected to hit the
> market.
Got it. Thanks for the detailed information.
prev parent reply other threads:[~2018-09-29 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 8:24 [GIT PULL] berlin dt64 changes for v4.20 Jisheng Zhang
2018-09-28 10:40 ` Arnd Bergmann
2018-09-29 1:33 ` Jisheng Zhang [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=20180929093309.08c32dca@xhacker.debian \
--to=jisheng.zhang@synaptics.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;
as well as URLs for NNTP newsgroup(s).