From: Greg KH <gregkh@linuxfoundation.org>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH] Staging: lustre: llite: refactor lov_object_fiemap()
Date: Mon, 7 Nov 2016 12:38:41 +0100 [thread overview]
Message-ID: <20161107113841.GA12277@kroah.com> (raw)
In-Reply-To: <AD95A5E8-3232-4528-83A2-5922FBE23C30@intel.com>
On Mon, Nov 07, 2016 at 10:56:19AM +0000, Xu, Bobijam wrote:
> * Change loff_t to u64 in lov_object_fiemap() since loff_t is a
> signed value type.
> * Add fiemap_for_stripe() to get file map extent from each stripe
> device.
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Bobi Jam <bobijam.xu@intel.com>
Why are you doing two different things in the same patch and also not
cc:ing the maintainers of the driver you are modifying?
Please break this up and fix the cc: issues.
thanks,
greg k-h
parent reply other threads:[~2016-11-07 11:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AD95A5E8-3232-4528-83A2-5922FBE23C30@intel.com>]
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=20161107113841.GA12277@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lustre-devel@lists.lustre.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.