Hello Linus,

Please also pull a few pstore updates,

The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:

  Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)

are available in the git repository at:

  git://git.infradead.org/users/cbou/linux-pstore.git tags/for-v3.7

for you to fetch changes up to 80c9d03c22f13a17df67b4b99a83ed5e9acf6093:

  pstore: Avoid recursive spinlocks in the oops_in_progress case (2012-09-20 
17:04:50 -0700)

----------------------------------------------------------------
1. We no longer ad-hoc to the function tracer "high level" infrastructure
   and no longer use its debugfs knobs. The change slightly touches
   kernel/trace directory, but it got the needed ack from Steven Rostedt:
   http://lkml.org/lkml/2012/8/21/688
2. Added maintainers entry;
3. A bunch of fixes, nothing special.

----------------------------------------------------------------
Anton Vorontsov (4):
      pstore/ram: Fix possible NULL dereference
      pstore/ram: Mark ramoops_pstore_write_buf() as notrace
      MAINTAINERS: Add pstore maintainers
      pstore/ftrace: Convert to its own enable/disable debugfs knob

Chuansheng Liu (1):
      pstore: Avoid recursive spinlocks in the oops_in_progress case

Jovi Zhang (1):
      pstore/ram: Add missing platform_device_unregister

Randy Dunlap (1):
      pstore/ram: Fix printk format warning

 Documentation/ramoops.txt      |  4 +-
 MAINTAINERS                    | 12 +++++
 fs/pstore/Kconfig              |  1 +
 fs/pstore/ftrace.c             | 96 +++++++++++++++++++++++++++++++++++-
 fs/pstore/internal.h           |  6 +++
 fs/pstore/platform.c           |  9 +++-
 fs/pstore/ram.c                | 28 ++++++-----
 include/linux/pstore.h         |  8 ---
 kernel/trace/trace_functions.c | 15 +-----
 9 files changed, 139 insertions(+), 40 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to