public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>,
	<linux-acpi@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] drivers/acpi: make evged.c explicitly non-modular
Date: Mon, 9 May 2016 15:59:29 -0400	[thread overview]
Message-ID: <20160509195928.GB18139@windriver.com> (raw)
In-Reply-To: <5730E671.8070201@codeaurora.org>

[Re: [PATCH] drivers/acpi: make evged.c explicitly non-modular] On 09/05/2016 (Mon 15:35) Sinan Kaya wrote:

> +Rafael,
> 
> On 5/9/2016 2:40 PM, Paul Gortmaker wrote:
> > The Makefile/Kconfig currently controlling compilation of this code is:
> > 
> > Makefile:acpi-$(CONFIG_ACPI_REDUCED_HARDWARE_ONLY) += evged.o
> > 
> > -
> > -module_platform_driver(ged_driver);
> > -MODULE_LICENSE("GPL v2");
> > +builtin_platform_driver(ged_driver);
> > 
> 
> Thanks, it looks good to me. I realized Rafael was missing in your post.
> I added him here.

Thanks for spotting that.  It looks like I fat fingered his "Cc:" line
into a "c:" at some point and I didn't notice his name was absent when
git gave me the summary of recipients before hitting send.  :-(

Would have been nice if git send-email had given me a warning, but I
guess there are so many different non-stanadard headers out there now,
it would be impossible to assume "c:" wasn't valid for someone....

P.
--

> 
> -- 
> Sinan Kaya
> Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

  reply	other threads:[~2016-05-09 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 18:40 [PATCH] drivers/acpi: make evged.c explicitly non-modular Paul Gortmaker
2016-05-09 19:35 ` Sinan Kaya
2016-05-09 19:59   ` Paul Gortmaker [this message]
2016-05-11  0:11     ` 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=20160509195928.GB18139@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okaya@codeaurora.org \
    --cc=rjw@rjwysocki.net \
    /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