From: Jens Axboe <axboe@fb.com>
To: Vishal Verma <vishal.l.verma@intel.com>, linux-nvdimm@lists.01.org
Cc: linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
linux-scsi@vger.kernel.org, NeilBrown <neilb@suse.com>,
Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [PATCH 1/3] badblocks: Add core badblock management code
Date: Tue, 24 Nov 2015 12:19:56 -0700 [thread overview]
Message-ID: <5654B85C.7000409@fb.com> (raw)
In-Reply-To: <1448066960-20119-2-git-send-email-vishal.l.verma@intel.com>
On 11/20/2015 05:49 PM, Vishal Verma wrote:
> Take the core badblocks implementation from md, and make it generally
> available. This follows the same style as kernel implementations of
> linked lists, rb-trees etc, where you can have a structure that can be
> embedded anywhere, and accessor functions to manipulate the data.
>
> The only changes in this copy of the code are ones to generalize
> function/variable names from md-specific ones. Also add init and free
> functions.
Split this into a .c file with the code.
--
Jens Axboe
next prev parent reply other threads:[~2015-11-24 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 0:49 [PATCH 0/3] Badblock tracking for gendisks Vishal Verma
2015-11-21 0:49 ` [PATCH 1/3] badblocks: Add core badblock management code Vishal Verma
2015-11-24 19:19 ` Jens Axboe [this message]
2015-11-21 0:49 ` [PATCH 2/3] block: Add badblock management for gendisks Vishal Verma
2015-11-24 15:34 ` Jeff Moyer
2015-11-24 19:03 ` Verma, Vishal L
2015-11-24 19:14 ` Jeff Moyer
2015-11-24 20:10 ` Verma, Vishal L
2015-11-24 21:31 ` Dan Williams
2015-11-25 15:37 ` Jeff Moyer
2015-11-25 17:55 ` Verma, Vishal L
2015-11-25 18:07 ` Jeff Moyer
2015-11-21 0:49 ` [PATCH 3/3] md: convert to use the generic badblocks code Vishal Verma
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=5654B85C.7000409@fb.com \
--to=axboe@fb.com \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=neilb@suse.com \
--cc=vishal.l.verma@intel.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).