From: Olof Johansson <olof@lixom.net>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [GIT PULL v2] ARM: mvebu: arm for v5.2 (#1)
Date: Wed, 15 May 2019 23:24:01 -0700 [thread overview]
Message-ID: <20190516062401.7wiffazf3sbrrmvk@localhost> (raw)
In-Reply-To: <87v9yw5525.fsf@FE-laptop>
On Tue, Apr 30, 2019 at 09:24:18AM +0200, Gregory CLEMENT wrote:
> Hi,
>
> Here is the second version first pull request for arm for mvebu for
> v5.2. I fixed the coding style issue dtecting by checkpatch in the
> commit "ARM: mvebu: fix a leaked reference by adding missing
> of_node_put"
>
> Gregory
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-arm-5.2-1
>
> for you to fetch changes up to 7af2ea3b29b1640f5aafe79d7c110ce66190c04a:
>
> ARM: mvebu: drop return from void function (2019-04-30 09:05:44 +0200)
>
> ----------------------------------------------------------------
> mvebu arm for 5.2 (part 1)
>
> - remove improper error message on kirkwood
> - a couple a clean-up patch generated from automatic tools
> - clean-up in assembly code allowing using LLVM
Merged into arm/late now. Thanks!
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-05-16 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 7:24 [GIT PULL v2] ARM: mvebu: arm for v5.2 (#1) Gregory CLEMENT
2019-05-13 15:16 ` Gregory CLEMENT
2019-05-16 6:12 ` Olof Johansson
2019-05-17 7:14 ` Gregory CLEMENT
2019-05-16 6:24 ` Olof Johansson [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=20190516062401.7wiffazf3sbrrmvk@localhost \
--to=olof@lixom.net \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=gregory.clement@bootlin.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
/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