All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Alex Hung <alex.hung@canonical.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] hp_wireless: remove unused header files
Date: Thu, 18 Jun 2015 14:56:20 -0700	[thread overview]
Message-ID: <20150618215620.GD121898@vmdeb7> (raw)
In-Reply-To: <1433928387-2818-1-git-send-email-alex.hung@canonical.com>

On Wed, Jun 10, 2015 at 05:26:27PM +0800, Alex Hung wrote:

No commit message again.

If you feel there is nothing to say in the commit message, do a git log search
for similar patches for examples of what is relevant. (There are several for
removing unused header files)

Please don't send another like this.

> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> ---
>  drivers/platform/x86/hp-wireless.c |    3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/drivers/platform/x86/hp-wireless.c b/drivers/platform/x86/hp-wireless.c
> index 4e4cc8b..731c69b 100644
> --- a/drivers/platform/x86/hp-wireless.c
> +++ b/drivers/platform/x86/hp-wireless.c
> @@ -18,11 +18,8 @@
>   *  51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
>   */
>  
> -#include <linux/kernel.h>
>  #include <linux/module.h>
> -#include <linux/init.h>
>  #include <linux/input.h>
> -#include <linux/platform_device.h>
>  #include <linux/acpi.h>
>  #include <acpi/acpi_bus.h>
>  

What was your motivation here? Did you observe a change in the driver? A
subsystem? Run a tool?

Note that acpi.h also includes acpi/acpi_bus.h, so it isn't strictly
necessary either.

Please explain your motivation and rationale. If it's worth preparing, building,
and testing, it's worth documenting.

-- 
Darren Hart
Intel Open Source Technology Center

      reply	other threads:[~2015-06-18 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  9:26 [PATCH] hp_wireless: remove unused header files Alex Hung
2015-06-18 21:56 ` Darren Hart [this message]

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=20150618215620.GD121898@vmdeb7 \
    --to=dvhart@infradead.org \
    --cc=alex.hung@canonical.com \
    --cc=platform-driver-x86@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.