From: Lukas Wunner <lukas@wunner.de>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: [PATCH 0/1] fixup! ACPI / utils: Add acpi_dev_present()
Date: Fri, 1 Jan 2016 22:52:15 +0100 [thread overview]
Message-ID: <cover.1451671935.git.lukas@wunner.de> (raw)
Hi Rafael,
I've just made the embarrassing discovery that I forgot to run checkpatch
before submitting 2d12b6b381ba ("ACPI / utils: Add acpi_dev_present()").
The commit compiles and works just fine but checkpatch complains about a
missing blank in a struct which I had moved verbatim from scan.c to
internal.h.
The commit is on your bleeding-edge and linux-next branches. If you're
still able to rebase, you may want to autosquash this fixup patch.
My apologies for the inconvenience.
Lukas
Lukas Wunner (1):
fixup! ACPI / utils: Add acpi_dev_present()
drivers/acpi/internal.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.8.5.2 (Apple Git-48)
next reply other threads:[~2016-01-01 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 21:52 Lukas Wunner [this message]
2016-01-01 21:52 ` [PATCH 1/1] fixup! ACPI / utils: Add acpi_dev_present() Lukas Wunner
2016-01-05 12:59 ` Rafael J. Wysocki
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=cover.1451671935.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).