Patchwork [GIT,PULL] ARM: orion/dove: v3.4 fixes

login
register
mail settings
Submitter Jason
Date May 14, 2012, 6:27 p.m.
Message ID <20120514182722.GM16338@titan.lakedaemon.net>
Download mbox
Permalink /patch/159109/
State New
Headers show

Pull-request

git://git.infradead.org/users/jcooper/linux.git orion_fixes_for_v3.4

Comments

Jason - May 14, 2012, 6:27 p.m.
The following changes since commit d48b97b403d23f6df0b990cee652bdf9a52337a3:

  Linux 3.4-rc6 (2012-05-06 15:07:32 -0700)

are available in the git repository at:
  git://git.infradead.org/users/jcooper/linux.git orion_fixes_for_v3.4

Alexander Clouter (5):
      crypto: mv_cesa requires on CRYPTO_HASH to build
      ARM: orion5x: ts78xx whitespace cleanups
      ARM: orion5x: ts78xx fix NAND resource off by one
      ARM: orion5x: remove PM dependency from ts78xx
      ARM: orion5x: ts78xx debugging changes

Andrew Lunn (3):
      Orion5x: Fix warning: struct pci_dev declared inside paramter list
      Orion5x: Fix Section mismatch warnings
      Dove: Fix Section mismatch warnings

Jason Cooper (1):
      Merge branch 'v3.4-rc6-cleanup-v2' of git://github.com/lunn/linux
into orion_fixes_for_v3.4

 arch/arm/mach-dove/common.c          |    2 +-
 arch/arm/mach-dove/mpp.c             |    8 ++--
 arch/arm/mach-orion5x/Kconfig        |    1 -
 arch/arm/mach-orion5x/addr-map.c     |    2 +-
 arch/arm/mach-orion5x/common.c       |    2 +-
 arch/arm/mach-orion5x/common.h       |    1 +
 arch/arm/mach-orion5x/ts78xx-fpga.h  |    6 ++--
 arch/arm/mach-orion5x/ts78xx-setup.c |   52
+++++++++++++++------------------
 drivers/crypto/Kconfig               |    1 +
 9 files changed, 36 insertions(+), 39 deletions(-)
Arnd Bergmann - May 14, 2012, 8:40 p.m.
On Monday 14 May 2012, Jason Cooper wrote:
> The following changes since commit d48b97b403d23f6df0b990cee652bdf9a52337a3:
> 
>   Linux 3.4-rc6 (2012-05-06 15:07:32 -0700)
> 
> are available in the git repository at:
>   git://git.infradead.org/users/jcooper/linux.git orion_fixes_for_v3.4
> 
> Alexander Clouter (5):
>       crypto: mv_cesa requires on CRYPTO_HASH to build
>       ARM: orion5x: ts78xx whitespace cleanups
>       ARM: orion5x: ts78xx fix NAND resource off by one
>       ARM: orion5x: remove PM dependency from ts78xx
>       ARM: orion5x: ts78xx debugging changes
> 
> Andrew Lunn (3):
>       Orion5x: Fix warning: struct pci_dev declared inside paramter list
>       Orion5x: Fix Section mismatch warnings
>       Dove: Fix Section mismatch warnings
> 
> Jason Cooper (1):
>       Merge branch 'v3.4-rc6-cleanup-v2' of git://github.com/lunn/linux
> into orion_fixes_for_v3.4
> 


Pulled into next/fixes, thanks!

I noticed that none of these are tagged for inclusion into stable. Is that
intentional? When sending bug fixes, please make sure that each patch that
you want to get applied on older kernel versions contains a
'Cc: stable@vger.kernel.org' line!

	Arnd
Arnd Bergmann - May 14, 2012, 8:45 p.m.
On Monday 14 May 2012, Jason Cooper wrote:
> The following changes since commit d48b97b403d23f6df0b990cee652bdf9a52337a3:
> 
>   Linux 3.4-rc6 (2012-05-06 15:07:32 -0700)
> 
> are available in the git repository at:
>   git://git.infradead.org/users/jcooper/linux.git orion_fixes_for_v3.4
> 
> Alexander Clouter (5):
>       crypto: mv_cesa requires on CRYPTO_HASH to build
>       ARM: orion5x: ts78xx whitespace cleanups
>       ARM: orion5x: ts78xx fix NAND resource off by one
>       ARM: orion5x: remove PM dependency from ts78xx
>       ARM: orion5x: ts78xx debugging changes
> 
> Andrew Lunn (3):
>       Orion5x: Fix warning: struct pci_dev declared inside paramter list
>       Orion5x: Fix Section mismatch warnings
>       Dove: Fix Section mismatch warnings
> 
> Jason Cooper (1):
>       Merge branch 'v3.4-rc6-cleanup-v2' of git://github.com/lunn/linux
> into orion_fixes_for_v3.4

I just noticed that you said 'for v3.4', not 'for v3.5'. We're really late
in the cycle now, so I would only take serious bug fixes and regressions,
everything else would better go into v3.5. Which of these are critical
and required for v3.4 (i.e. which ones would you backport if v3.4 was
already released)?

	Arnd
Jason - May 14, 2012, 9:40 p.m.
Arnd Bergmann <arnd@arndb.de> wrote:

>On Monday 14 May 2012, Jason Cooper wrote:
>> The following changes since commit
>d48b97b403d23f6df0b990cee652bdf9a52337a3:
>> 
>>   Linux 3.4-rc6 (2012-05-06 15:07:32 -0700)
>> 
>> are available in the git repository at:
>>   git://git.infradead.org/users/jcooper/linux.git
>orion_fixes_for_v3.4
>> 
>> Alexander Clouter (5):
>>       crypto: mv_cesa requires on CRYPTO_HASH to build
>>       ARM: orion5x: ts78xx whitespace cleanups
>>       ARM: orion5x: ts78xx fix NAND resource off by one
>>       ARM: orion5x: remove PM dependency from ts78xx
>>       ARM: orion5x: ts78xx debugging changes
>> 
>> Andrew Lunn (3):
>>       Orion5x: Fix warning: struct pci_dev declared inside paramter
>list
>>       Orion5x: Fix Section mismatch warnings
>>       Dove: Fix Section mismatch warnings
>> 
>> Jason Cooper (1):
>>       Merge branch 'v3.4-rc6-cleanup-v2' of
>git://github.com/lunn/linux
>> into orion_fixes_for_v3.4
>
>I just noticed that you said 'for v3.4', not 'for v3.5'. We're really
>late
>in the cycle now, so I would only take serious bug fixes and
>regressions,
>everything else would better go into v3.5. Which of these are critical
>and required for v3.4 (i.e. which ones would you backport if v3.4 was
>already released)?
>
>	Arnd

Yes, my mistake.  I thought what Andrew tested was fixes for v3.4.

The only thing I would push to stable and v3.4 is the mv_cesa fix.  I'll send an amended pull request in a few hours.

Thx,

Jason.