From: Kent Overstreet <koverstreet@google.com>
To: Emil Goode <emilgoode@gmail.com>
Cc: neilb@suse.de, linux-bcache@vger.kernel.org,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] bcache: Fix incompatible pointer type warning
Date: Thu, 9 May 2013 13:57:01 -0700 [thread overview]
Message-ID: <20130509205701.GC15040@moria.home.lan> (raw)
In-Reply-To: <1368131966-17512-1-git-send-email-emilgoode@gmail.com>
On Thu, May 09, 2013 at 10:39:26PM +0200, Emil Goode wrote:
> The function pointer release in struct block_device_operations
> should point to functions declared as void.
Looks like .release just changed to returning void in the merge window -
thanks, applied
prev parent reply other threads:[~2013-05-09 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 20:39 [PATCH] bcache: Fix incompatible pointer type warning Emil Goode
2013-05-09 20:57 ` Kent Overstreet [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=20130509205701.GC15040@moria.home.lan \
--to=koverstreet@google.com \
--cc=emilgoode@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).