public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Marek Behun <marek.behun@nic.cz>
Cc: arm@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org,
	Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [GIT PULL] Turris Mox Moxtet bus
Date: Sun, 28 Apr 2019 12:06:34 -0700	[thread overview]
Message-ID: <20190428190634.3i6tjpflqezd6xkq@localhost> (raw)
In-Reply-To: <20190328192232.4b5c993a@nic.cz>

Hi Marek,

On Thu, Mar 28, 2019 at 07:22:32PM +0100, Marek Behun wrote:
> Hello arm-soc maintainers,
> 
> please pull the implementation of the Moxtet bus driver into arm-soc/for-next.
> Moxtet is a small bus found on Turris Mox.
> The patches are reviewed by Linus Walleij and Rob Herring.
> 
> Thanks,
> Marek
> 
> The following changes since commit 93958742192e7956d05989836ada9071f9ffe42e:
> 
>   arm64: tegra: Disable CQE Support for SDMMC4 on Tegra186 (2019-03-25 17:12:20 +0100)
> 
> are available in the Git repository at:
> 
>   https://gitlab.labs.nic.cz/turris/mox-kernel.git/ arm-soc-moxtet-bus
> 
> for you to fetch changes up to cea960603584ff05ae6dba647d1641508e5998b4:
> 
>   dt-bindings: gpio: Document GPIOs via Moxtet bus (2019-03-28 19:03:01 +0100)

There are several things that should be addressed in this pull request:

 - Please use a signed tag. In that tag, you should provide a description of
   the pull request similar to above (but with a bit more context, i.e.
   a high-level description of the functionality and why we should merge it.
   Similar to cover letters for patch series.
 - For said signed tag, please get a PGP key established and get other
   developers/maintainers to sign it for you.
 - Nit: If you pipe the 'git pull-request' output to cat, or redirect it to
   a file, it'll size the diffstat such that it fits in 80 columns and won't
   wrap as per below.


I know time is getting short for the next release at the moment and
getting keys signed might take some time, so if you prefer to send the
contents as a patch series and have us apply that, feel free to do so.



-Olof

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

  reply	other threads:[~2019-04-28 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 18:22 [GIT PULL] Turris Mox Moxtet bus Marek Behun
2019-04-28 19:06 ` Olof Johansson [this message]
2019-04-28 21:40   ` Marek Behun

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=20190428190634.3i6tjpflqezd6xkq@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marek.behun@nic.cz \
    /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