All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	arm@kernel.org, soc@kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: mvebu: fixes for v5.13 (#1)
Date: Wed, 23 Jun 2021 18:56:33 -0700	[thread overview]
Message-ID: <20210624015633.GA19649@lx2k> (raw)
In-Reply-To: <87eecx0w6s.fsf@BL-laptop>

On Sun, Jun 20, 2021 at 10:36:27AM +0200, Gregory CLEMENT wrote:
> Hi,
> 
> Here is the first pull request for fixes for mvebu for v5.13.
> 
> Gregory
> 
> The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
> 
>   Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-fixes-5.13-1
> 
> for you to fetch changes up to fae20160992269431507708fb74c1fd9f3c309c1:
> 
>   firmware: turris-mox-rwtm: show message about HWRNG registration (2021-06-17 14:55:09 +0200)
> 
> ----------------------------------------------------------------
> mvebu fixes for 5.13 (part 1)
> 
> Few fixes for the Turris Mox rWTM firmware found on the Armada 3700
> SoCs.

Looks like these fixes were posted in March(!!), and obviously can't be all
that urgent if it's taken until now to apply them. Doesn't seem like a severe
enough regression to go in at -rc7, so I'll queue it for the merge window.

Thanks,

-Olof

WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	arm@kernel.org, soc@kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: mvebu: fixes for v5.13 (#1)
Date: Wed, 23 Jun 2021 18:56:33 -0700	[thread overview]
Message-ID: <20210624015633.GA19649@lx2k> (raw)
Message-ID: <20210624015633.9x-rsg07ETSKEtrZYG-0H3_LylMsIli6rdvYCcyDa_4@z> (raw)
In-Reply-To: <87eecx0w6s.fsf@BL-laptop>

On Sun, Jun 20, 2021 at 10:36:27AM +0200, Gregory CLEMENT wrote:
> Hi,
> 
> Here is the first pull request for fixes for mvebu for v5.13.
> 
> Gregory
> 
> The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
> 
>   Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-fixes-5.13-1
> 
> for you to fetch changes up to fae20160992269431507708fb74c1fd9f3c309c1:
> 
>   firmware: turris-mox-rwtm: show message about HWRNG registration (2021-06-17 14:55:09 +0200)
> 
> ----------------------------------------------------------------
> mvebu fixes for 5.13 (part 1)
> 
> Few fixes for the Turris Mox rWTM firmware found on the Armada 3700
> SoCs.

Looks like these fixes were posted in March(!!), and obviously can't be all
that urgent if it's taken until now to apply them. Doesn't seem like a severe
enough regression to go in at -rc7, so I'll queue it for the merge window.

Thanks,

-Olof

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

  reply	other threads:[~2021-06-24  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20  8:36 [GIT PULL] ARM: mvebu: fixes for v5.13 (#1) Gregory CLEMENT
2021-06-20  8:36 ` Gregory CLEMENT
2021-06-24  1:56 ` Olof Johansson [this message]
2021-06-24  1:56   ` Olof Johansson
2021-06-24  2:40 ` patchwork-bot+linux-soc

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=20210624015633.GA19649@lx2k \
    --to=olof@lixom.net \
    --cc=andrew@lunn.ch \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=gregory.clement@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=soc@kernel.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 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.