public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: defconfig for v4.7 (#2)
Date: Sat, 30 Apr 2016 18:46:22 +0200	[thread overview]
Message-ID: <87shy3qc2p.fsf@free-electrons.com> (raw)
In-Reply-To: <20160430181913.3ceee35b@free-electrons.com> (Thomas Petazzoni's message of "Sat, 30 Apr 2016 18:19:13 +0200")

Hi Thomas,
 
 On sam., avril 30 2016, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Fri, 29 Apr 2016 16:35:19 +0200, Gregory CLEMENT wrote:
>> Hi,
>> 
>> Here is the second pull request for defconfig for mvebu for v4.7.
>> 
>> Gregory
>> 
>> The following changes since commit 23d2af622de748bf57d31a4125d06d183c29e908:
>> 
>>   ARM: mvebu_v5_defconfig: Switching to the new Marvell's cryptographic engine driver (2016-04-14 18:57:19 +0200)
>> 
>> are available in the git repository at:
>> 
>>   git://git.infradead.org/linux-mvebu.git tags/mvebu-defconfig-4.7-2
>> 
>> for you to fetch changes up to acef3efe096d8de9f115f0d9e9c681147887bcac:
>> 
>>   arm64: marvell: enable AP806 and CP110 syscon driver (2016-04-26 15:20:51 +0200)
>> 
>> ----------------------------------------------------------------
>> mvebu defconfig for 4.7 (part 2)
>> 
>> - enable AP806 and CP110 syscon driver in arm64 defconfig
>> 
>> ----------------------------------------------------------------
>> Thomas Petazzoni (1):
>>       arm64: marvell: enable AP806 and CP110 syscon driver
>
> I am not sure how important that is, but this patch is in your
> defconfig branch, but it's not defconfig related, and the same patch is
> already in your mvebu-arm64-4.7-1 branch.
>
> However, you indeed forgot my arm64 defconfig patch, so I believe there
> might have been a mistake on your side here, unless I missed something
> of course!

You are right: I applied the wrong patch in the mvebu/defconfig
branch. Sorry for that. I am about to resend a PR for this branch.

Thanks,

Gregory

>
> Thanks!
>
> Thomas
> -- 
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2016-04-30 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 14:35 [GIT PULL] ARM: mvebu: defconfig for v4.7 (#2) Gregory CLEMENT
2016-04-30 16:19 ` Thomas Petazzoni
2016-04-30 16:46   ` Gregory CLEMENT [this message]
2016-05-10 12:05 ` Arnd Bergmann
2016-05-10 12:13   ` Arnd Bergmann
2016-05-10 14:42     ` Gregory CLEMENT

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=87shy3qc2p.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.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