From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: [PATCH - mdadm] Fix some issues found by clang
Date: Fri, 07 Oct 2016 11:48:58 -0400 [thread overview]
Message-ID: <wrfjk2dkdus5.fsf@redhat.com> (raw)
In-Reply-To: <8737k84xuf.fsf@notabene.neil.brown.name> (NeilBrown's message of "Fri, 07 Oct 2016 14:55:20 +1100")
NeilBrown <neilb@suse.com> writes:
> The clang compiler complained about each of these.
>
> The mdmon.h error will only affect 'far' RAID10 arrays using intel or DDF
> metadata, and there is no such thing.
>
> The mdopen.c will cause a problem if there are no free md device
> numbers in the first 512. That is fairly unlikely.
>
> The restripe.c error would only affect the 'test_stripe' command, and
> probably doesn't change its behaviour.
>
> The super-intel.c fix is purely cosmetic.
>
> Signed-off-by: NeilBrown <neilb@suse.com>
Oh neat! There are some real gems in there. Now I don't feel so bad
about the brown paper bag bug I found in my wireless driver last night
:)
Applied!
Thanks,
Jes
prev parent reply other threads:[~2016-10-07 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 3:55 [PATCH - mdadm] Fix some issues found by clang NeilBrown
2016-10-07 15:48 ` 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=wrfjk2dkdus5.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@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