From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: "James E.J. Bottomley" <JBottomley@parallels.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: scsi: #define missing include guards
Date: Fri, 22 Aug 2014 15:28:54 +0200 [thread overview]
Message-ID: <87iolkslex.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <1408711053-14129-1-git-send-email-linux@rasmusvillemoes.dk> (Rasmus Villemoes's message of "Fri, 22 Aug 2014 14:37:33 +0200")
Rasmus Villemoes <linux@rasmusvillemoes.dk> writes:
> The four files aha1542.h, aha1740.h, gvp11.h and mvme147.h under
> drivers/scsi/ contain two-thirds of an include guard, but do not
> elsewhere.
>
Argh, git commit ate a line because it happened to start with #. This
was supposed to be something like "...but do not #define the macro. git
grep says that the macro names are not defined elsewhere."
Rasmus
next prev parent reply other threads:[~2014-08-22 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 12:37 [PATCH] drivers: scsi: #define missing include guards Rasmus Villemoes
2014-08-22 13:28 ` Rasmus Villemoes [this message]
2014-08-24 15:35 ` Christoph Hellwig
2014-08-25 8:10 ` [PATCH v2] " Rasmus Villemoes
2014-08-26 9:26 ` [PATCH] " Hannes Reinecke
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=87iolkslex.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=JBottomley@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox