All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Erik Kaneda <erik.kaneda@intel.com>
Subject: [PATCH v1 0/6] ACPI:  Clean up printing messages in some source files
Date: Wed, 20 Jan 2021 19:56:12 +0100	[thread overview]
Message-ID: <2809410.8bz27usjlQ@kreacher> (raw)

Hi,

This series cleans up messaging in some source files under drivers/acpi/
and get rids of some debug code pieces that aren't needed any more.

The primary goal here was to get rid of things like ACPI_DEBUG_PRINT()
or ACPI_EXCEPTION() from non-ACPICA code (they are specific to ACPICA and
should not be used outside of it) and allow the usual dynamic debug to
be used in the files in question instead, but also there are some
cleanups related to the raw printk() usage and so on.

Please refer to patch changelogs for details.

Thanks!




             reply	other threads:[~2021-01-20 19:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 18:56 Rafael J. Wysocki [this message]
2021-01-20 18:57 ` [PATCH v1 1/6] ACPI: power: Clean up printing messages Rafael J. Wysocki
2021-01-20 18:58 ` [PATCH v1 2/6] ACPI: PM: " Rafael J. Wysocki
2021-01-20 18:59 ` [PATCH v1 3/6] ACPI: bus: " Rafael J. Wysocki
2021-01-20 18:59 ` [PATCH v1 4/6] ACPI: scan: " Rafael J. Wysocki
2021-01-21 21:24   ` kernel test robot
2021-01-21 21:24     ` kernel test robot
2021-01-20 19:00 ` [PATCH v1 5/6] ACPI: utils: " Rafael J. Wysocki
2021-01-20 19:01 ` [PATCH v1 6/6] ACPI: bus: Drop ACPI_BUS_COMPONENT which is not used any more Rafael J. Wysocki
2021-01-20 20:09 ` [PATCH v1 0/6] ACPI: Clean up printing messages in some source files Joe Perches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2809410.8bz27usjlQ@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=erik.kaneda@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.