From: jeff@garzik.org (Jeff Garzik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mark empty gpio.h files empty
Date: Fri, 28 Oct 2011 16:36:58 -0400 [thread overview]
Message-ID: <4EAB126A.5090507@garzik.org> (raw)
In-Reply-To: <1319833142-4764-1-git-send-email-linus.walleij@linaro.org>
On 10/28/2011 04:19 PM, Linus Walleij wrote:
> It is generally a better idea to make intentionally empty files
> contain the human-readable /* empty */ comment, also it makes
> the files play nice with "make distclean".
>
> Reported-by: Jeff Garzik<jeff@garzik.org>
> Signed-off-by: Linus Walleij<linus.walleij@linaro.org>
Thanks!
Acked-by: Jeff Garzik <jgarzik@redhat.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jeff@garzik.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, swarren@nvidia.com, olof@lixom.net,
ben@decadent.org.uk, arnaud.patard@rtp-net.org,
grant.likely@secretlab.ca, w.sang@pengutronix.de, bs14@csr.com
Subject: Re: [PATCH] ARM: mark empty gpio.h files empty
Date: Fri, 28 Oct 2011 16:36:58 -0400 [thread overview]
Message-ID: <4EAB126A.5090507@garzik.org> (raw)
In-Reply-To: <1319833142-4764-1-git-send-email-linus.walleij@linaro.org>
On 10/28/2011 04:19 PM, Linus Walleij wrote:
> It is generally a better idea to make intentionally empty files
> contain the human-readable /* empty */ comment, also it makes
> the files play nice with "make distclean".
>
> Reported-by: Jeff Garzik<jeff@garzik.org>
> Signed-off-by: Linus Walleij<linus.walleij@linaro.org>
Thanks!
Acked-by: Jeff Garzik <jgarzik@redhat.com>
next prev parent reply other threads:[~2011-10-28 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 20:19 [PATCH] ARM: mark empty gpio.h files empty Linus Walleij
2011-10-28 20:19 ` Linus Walleij
2011-10-28 20:36 ` Jeff Garzik [this message]
2011-10-28 20:36 ` Jeff Garzik
2011-10-29 11:06 ` Grant Likely
2011-10-29 11:06 ` Grant Likely
2011-10-31 15:50 ` Linus Walleij
2011-10-31 15:50 ` Linus Walleij
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=4EAB126A.5090507@garzik.org \
--to=jeff@garzik.org \
--cc=linux-arm-kernel@lists.infradead.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.