From: Jes Sorensen <jes.sorensen@gmail.com>
To: Zhilong Liu <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mdadm/util: unify stat checking blkdev into function
Date: Fri, 5 May 2017 11:06:47 -0400 [thread overview]
Message-ID: <e62d1997-656e-9383-8c62-13cf4b0d422c@gmail.com> (raw)
In-Reply-To: <20170505030941.14911-1-zlliu@suse.com>
On 05/04/2017 11:09 PM, Zhilong Liu wrote:
> declare function stat_is_blkdev() to integrate repeated stat
> checking blkdev operations, it returns 'true/1' when it is a
> block device, and returns 'false/0' when it isn't.
> The devname is necessary parameter, *rdev is optional, parse
> the pointer of dev_t *rdev, if valid, assigned device number
> to dev_t *rdev, if NULL, ignores.
Both applied!
Jes
prev parent reply other threads:[~2017-05-05 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 12:16 [PATCH v1 0/2] unify stat and fstat checking blkdev into functions Zhilong Liu
2017-05-04 12:16 ` [PATCH v1 1/2] mdadm/util: unify fstat checking blkdev into function Zhilong Liu
2017-05-04 12:16 ` [PATCH v1 2/2] mdadm/util: unify stat " Zhilong Liu
2017-05-04 15:33 ` Jes Sorensen
2017-05-05 3:09 ` [PATCH v2 " Zhilong Liu
2017-05-05 15:06 ` Jes Sorensen [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=e62d1997-656e-9383-8c62-13cf4b0d422c@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=zlliu@suse.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;
as well as URLs for NNTP newsgroup(s).