From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH REPOST] rbd: kill ceph_osd_req_op->flags
Date: Wed, 16 Jan 2013 19:01:29 -0800 [thread overview]
Message-ID: <50F76989.6070509@inktank.com> (raw)
In-Reply-To: <50E6EB40.3050701@inktank.com>
On 01/04/2013 06:46 AM, Alex Elder wrote:
> The flags field of struct ceph_osd_req_op is never used, so just get
> rid of it.
>
> Signed-off-by: Alex Elder <elder@inktank.com>
> ---
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
> include/linux/ceph/osd_client.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/linux/ceph/osd_client.h
> b/include/linux/ceph/osd_client.h
> index 2b04d05..69287cc 100644
> --- a/include/linux/ceph/osd_client.h
> +++ b/include/linux/ceph/osd_client.h
> @@ -157,7 +157,6 @@ struct ceph_osd_client {
>
> struct ceph_osd_req_op {
> u16 op; /* CEPH_OSD_OP_* */
> - u32 flags; /* CEPH_OSD_FLAG_* */
> union {
> struct {
> u64 offset, length;
>
prev parent reply other threads:[~2013-01-17 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 14:46 [PATCH REPOST] rbd: kill ceph_osd_req_op->flags Alex Elder
2013-01-17 3:01 ` Josh Durgin [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=50F76989.6070509@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@inktank.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