All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	arm@kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	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: Mon, 13 May 2019 17:16:27 +0200	[thread overview]
Message-ID: <87sgti1j1w.fsf@FE-laptop> (raw)
In-Reply-To: <87v9yw5525.fsf@FE-laptop>

Arnd, Olof, 

> 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"

Any news about this PR?

I sent it less than 24 hours after being rejected by Olof because of a
missing space, so I hope this branch will be finally merged.

Thanks,

Gregory

>
> 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
>
> ----------------------------------------------------------------
> Chris Packham (1):
>       ARM: mvebu: kirkwood: remove error message when retrieving mac address
>
> Nicholas Mc Guire (1):
>       ARM: mvebu: drop return from void function
>
> Stefan Agner (2):
>       ARM: mvebu: drop unnecessary label
>       ARM: mvebu: prefix coprocessor operand with p
>
> Wen Yang (1):
>       ARM: mvebu: fix a leaked reference by adding missing of_node_put
>
>  arch/arm/mach-mvebu/board-v7.c     |  1 -
>  arch/arm/mach-mvebu/coherency_ll.S |  2 +-
>  arch/arm/mach-mvebu/kirkwood.c     |  2 --
>  arch/arm/mach-mvebu/pm-board.c     | 11 ++++++++---
>  arch/arm/mach-mvebu/pmsu_ll.S      |  3 +--
>  5 files changed, 10 insertions(+), 9 deletions(-)
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

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

  reply	other threads:[~2019-05-13 15:16 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 [this message]
2019-05-16  6:12   ` Olof Johansson
2019-05-17  7:14     ` Gregory CLEMENT
2019-05-16  6:24 ` Olof Johansson

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=87sgti1j1w.fsf@FE-laptop \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --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 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.