From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Tomasz Majchrzak <tomasz.majchrzak@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] imsm: enable bad block support for imsm metadata
Date: Thu, 29 Dec 2016 14:29:03 -0500 [thread overview]
Message-ID: <wrfjzijefsao.fsf@redhat.com> (raw)
In-Reply-To: <1482914287-17630-1-git-send-email-tomasz.majchrzak@intel.com> (Tomasz Majchrzak's message of "Wed, 28 Dec 2016 09:38:07 +0100")
Tomasz Majchrzak <tomasz.majchrzak@intel.com> writes:
> Enable bad block support for imsm metadata as commit e522751d605d
> ("seq_file: reset iterator to first record for zero offset") has been
> accepted in upstream kernel. Prior to that patch mdmon had not been able
> to read bad blocks sysfs file.
>
> Signed-off-by: Tomasz Majchrzak <tomasz.majchrzak@intel.com>
> ---
> super-intel.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied!
Thanks,
Jes
prev parent reply other threads:[~2016-12-29 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 8:38 [PATCH] imsm: enable bad block support for imsm metadata Tomasz Majchrzak
2016-12-29 19:29 ` 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=wrfjzijefsao.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=tomasz.majchrzak@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).