Message ID | 87pot8sct4.fsf@free-electrons.com |
---|---|
State | New |
Headers | show |
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! Thanks! Thomas
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
On Friday 29 April 2016 16:35:19 Gregory CLEMENT wrote: > mvebu defconfig for 4.7 (part 2) > > - enable AP806 and CP110 syscon driver in arm64 defconfig > > Merged into next/defconfig, thanks! Arnd
On Tuesday 10 May 2016 14:05:48 Arnd Bergmann wrote: > On Friday 29 April 2016 16:35:19 Gregory CLEMENT wrote: > > mvebu defconfig for 4.7 (part 2) > > > > - enable AP806 and CP110 syscon driver in arm64 defconfig > > > > > > Merged into next/defconfig, thanks! > I ended up undoing the merge before I pushed it out to the git server as I noticed you have both arm and arm64 changes in there. Can you still split up the branch in two? Arnd
Hi Arnd, On mar., mai 10 2016, Arnd Bergmann <arnd@arndb.de> wrote: > On Tuesday 10 May 2016 14:05:48 Arnd Bergmann wrote: >> On Friday 29 April 2016 16:35:19 Gregory CLEMENT wrote: >> > mvebu defconfig for 4.7 (part 2) >> > >> > - enable AP806 and CP110 syscon driver in arm64 defconfig >> > >> > >> >> Merged into next/defconfig, thanks! >> > > I ended up undoing the merge before I pushed it out to the git server > as I noticed you have both arm and arm64 changes in there. > > Can you still split up the branch in two? As seen on IRC I am about to send a PR with a new mvebu/defconfig64 branch as the only change here was related to arm64. Gregory > > Arnd