From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: joseph daniel <josephdanielwalter@gmail.com>
Cc: Martyn Welch <martyn.welch@ge.com>,
Gerard Snitselaar <dev@snitselaar.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/vme: Remove version.h include
Date: Sun, 29 Apr 2012 21:28:49 -0400 [thread overview]
Message-ID: <20120430012849.GB12956@kroah.com> (raw)
In-Reply-To: <1335694022-8819-1-git-send-email-josephdanielwalter@gmail.com>
On Sun, Apr 29, 2012 at 04:07:02PM +0600, joseph daniel wrote:
> There are version.h includes that are not needed as make versioncheck reports.
> files:
> 1. drivers/staging/vme/devices/vme_pio2_core.c
> 2. drivers/staging/vme/devices/vme_pio2_gpio.c
>
> Signed-off-by: joseph daniel <josephdanielwalter@gmail.com>
This is already in linux-next as well, sorry.
greg k-h
prev parent reply other threads:[~2012-04-30 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 10:07 [PATCH] staging/vme: Remove version.h include joseph daniel
2012-04-30 1:28 ` Greg Kroah-Hartman [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=20120430012849.GB12956@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dev@snitselaar.org \
--cc=devel@driverdev.osuosl.org \
--cc=josephdanielwalter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martyn.welch@ge.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).