Linaro-2.6.35-1010.17 tracking bug

Bug #686071 reported by Tim Gardner
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-linaro (Ubuntu)
Invalid
Undecided
Unassigned
Maverick
Fix Released
Undecided
John Rigby
linux-meta-linaro (Ubuntu)
Invalid
Undecided
Unassigned
Maverick
Fix Released
Undecided
John Rigby

Bug Description

Stable updates, etc.

Tim Gardner (timg-tpi)
Changed in linux-linaro (Ubuntu):
status: New → Invalid
Tim Gardner (timg-tpi)
Changed in linux-linaro (Ubuntu Maverick):
assignee: nobody → John Rigby (jcrigby)
status: New → Fix Committed
summary: - Linaro-2.6.35-1008.15 tracking bug
+ Linaro-2.6.35-1010.17 tracking bug
Changed in linux-meta-linaro (Ubuntu):
status: New → Invalid
Tim Gardner (timg-tpi)
Changed in linux-meta-linaro (Ubuntu Maverick):
assignee: nobody → John Rigby (jcrigby)
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

I'd really appreciate if kernel SRUs could properly prepare all the referenced buts for SRUs, i. e. add proper Ubuntu package tasks ("linux-linaro (Ubuntu)") with a maverick task, and also set the natty status.

tags: added: verification-needed
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted linux-linaro into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Martin - With regard to comment #1, is that really worth the effort? Its simply not possible to subject these ARM vendor kernels to SRU policy.

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 686071] Re: Linaro-2.6.35-1010.17 tracking bug

Tim Gardner [2010-12-15 14:50 -0000]:
> Martin - With regard to comment #1, is that really worth the effort? Its
> simply not possible to subject these ARM vendor kernels to SRU policy.

Not doing so makes it much harder to see for bug reporters when a fix
has been proposed and released. After all, don't we expect testing
feedback from them as well?

Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted linux-meta-linaro into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Revision history for this message
Martin Pitt (pitti) wrote :

Accepting the -meta package took a while, as I can't do that right away with accepting the main kernel, as it would then build against the same old ABI again. Would it be possible to add a build dependency against the new kernel ABI somehow, so that the -meta build is guaranteed to wait until the corresponding kernel has been built, NEWed, and published? That would speed up accepting the metapackage a lot.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-linaro - 2.6.35-1010.17

---------------
linux-linaro (2.6.35-1010.17) maverick-proposed; urgency=low

  [ Tim Gardner ]

  * Stable updates tracking bug
    - LP: #686071

  [ John Rigby ]

  * LINARO: [CONFIG] Enable CONFIG_PERF_EVENTS for all flavours
    - LP: #683195
  * LINARO: [CONFIG] Enable CONFIG_POSIX_MQUEUE for all flavours
    - LP: #646419

  [ Ubuntu Kernel ]

  * Ubuntu-2.6.35-24.42
  * Ubuntu-2.6.35-23.41
  * Ubuntu-2.6.35-23.39
  * Ubuntu-2.6.35-23.38

  [ Upstream Stable Kernels ]

  * Linux 2.6.35.7
  * Linux 2.6.35.8
  * Linux 2.6.35.9

  [ linux-linaro-2.6.35 ]

  * ARM: perf-events: squash compiler warning
  * ARM: atomic64: use generic implementation for OABI configurations
  * ARM: backtrace: fix calculation of thread stack base
  * omap4: Update id.c and cpu.h for es2.0
  * omap4: l2x0: Fix init parameter for es2.0
  * omap4: Panda: Add DEBUG_LL support
  * omap4: Fix bootup crash observed with higher CPU clocks
  * Revert "Versatile Express: add support for local timers on CA9X4 daughterboard"
  * Revert "Revert "Versatile Express: add support for local timers on CA9X4 daughterboard""
  * omap: Use CONFIG_SMP for test_for_ipi and test_for_ltirq
  * omap: Fix sev instruction usage for multi-omap
  * USB: musb: Kill board specific pinmux from driver file
  * ARM: Do not enable SWP emulation if CPU_V6 && CPU_V7
  * omap3: id: fix 3630 rev detection
  * mfd: Adding twl6030 mmc card detect support for MMC1
  * omap4: pandaboard: fix up mmc card detect logic
  * OMAP4 ES2: HSMMC soft reset change
  * omap4 hsmmc: Fix the init if CONFIG_MMC_OMAP_HS is not set
  * omap4: pandaboard: Fix the init if CONFIG_MMC_OMAP_HS is not set
  * ARM: oprofile: fix merge conflict introduced by cd2cc211
  * ARM: Fix find_next_zero_bit and related assembly
  * OMAP3: PRCM: Consider UART4 for 3630 chip in prcm_setup_regs
  * OMAP clock: Add uart4_ick/fck definitions for 3630
  * OMAP3: serial: Fix uart4 handling for 3630
    - LP: #627512
  * omap: serial: Fix the boot-up crash/reboot without CONFIG_PM
  * OMAP: some definitions extracted from commit 046465b76a

linux-linaro (2.6.35-1009.16) maverick-proposed; urgency=low

  [ Ubuntu Kernel ]

  * Ubuntu-2.6.35-23.36
  * Ubuntu-2.6.35-23.37
  * Ubuntu-2.6.35-22.35

  [ John Rigby ]

  * LINARO: Update configs
    - LP: #672656
  * LINARO: Turn on and enforce PM CONFIG options
    - LP: #672791
 -- John Rigby <email address hidden> Thu, 02 Dec 2010 23:23:56 -0700

Changed in linux-linaro (Ubuntu Maverick):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-meta-linaro - 2.6.35.1010.14

---------------
linux-meta-linaro (2.6.35.1010.14) maverick-proposed; urgency=low

  * Linaro Maverick ABI 1010 (2.6.35-1010.17)
    - LP: #686071
 -- John Rigby <email address hidden> Fri, 03 Dec 2010 21:45:54 -0700

Changed in linux-meta-linaro (Ubuntu Maverick):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.