Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753551Ab3F1UOT (ORCPT ); Fri, 28 Jun 2013 16:14:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43619 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751635Ab3F1UOQ (ORCPT ); Fri, 28 Jun 2013 16:14:16 -0400 From: Lenny Szubowicz To: tony.luck@intel.com, cbouatmailru@gmail.com, matt.fleming@intel.com, linux-kernel@vger.kernel.org Cc: n.hamaguchi@jp.fujitsu.com, dzickus@redhat.com Subject: [PATCH 0/3] acpi: Eliminate misleading erst pstore console message Date: Fri, 28 Jun 2013 16:14:08 -0400 Message-Id: <1372450451-8790-1-git-send-email-lszubowi@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1326 Lines: 34 On systems that have a valid ACPI ERST table, if the pstore.backend kernel parameter selects a specific facility other than erst, then during boot the following console message is displayed: ERST: Could not register with persistent store This message makes it seem that something has gone wrong. In fact the same message is used when you want ERST to be used by pstore and some real error precludes registration. The primary purpose of this 3 patch set is to avoid displaying this console error message when another facility is explicitly selected as the backend for pstore. Details are in the individual patches. Lenny Szubowicz (3): pstore: Return unique error if backend registration excluded by kernel param acpi: Eliminate console msg if pstore.backend excludes ERST efivars: If pstore_register fails, free unneeded pstore buffer drivers/acpi/apei/erst.c | 20 ++++++++++++++------ drivers/firmware/efi/efi-pstore.c | 6 +++++- fs/pstore/platform.c | 11 ++++++----- 3 files changed, 25 insertions(+), 12 deletions(-) -- 1.8.2.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/