All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: Mike Miller <mike.miller@hp.com>,
	iss_storagedev@hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block/cciss: Close continue statement with semicolon to fix build
Date: Tue, 21 Dec 2010 11:09:52 +0100	[thread overview]
Message-ID: <4D107CF0.5090007@kernel.dk> (raw)
In-Reply-To: <1292924526-10850-1-git-send-email-stefan@datenfreihafen.org>

On 2010-12-21 10:42, Stefan Schmidt wrote:
> This fixes the following build error:
> drivers/block/cciss.c: In function ‘cciss_revalidate’:
> drivers/block/cciss.c:2839: error: expected ‘;’ before ‘if’
> make[2]: *** [drivers/block/cciss.o] Error 1

It's already included in Linus' git.

-- 
Jens Axboe


  reply	other threads:[~2010-12-21 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21  9:42 [PATCH] block/cciss: Close continue statement with semicolon to fix build Stefan Schmidt
2010-12-21 10:09 ` Jens Axboe [this message]
2010-12-21 10:31   ` Stefan Schmidt
2010-12-21 10:32     ` Jens Axboe
2010-12-21 10:39       ` Stefan Schmidt

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=4D107CF0.5090007@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=iss_storagedev@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.miller@hp.com \
    --cc=stefan@datenfreihafen.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.