md.4 | 34 17 + 17 - 0 !
mdadm.8.in | 16 8 + 8 - 0 !
mdmon.8 | 2 1 + 1 - 0 !
3 files changed, 26 insertions(+), 26 deletions(-)

 fix typos and macro issues in manpages
 (Closes: #915182, #916946, #962946, #933773).

mdmonitor.c | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 add host name to default mailfrom (closes: #1006464).
 The host on which the error occurred is mentioned in the subject and also in
 the message body, but some may find it useful in the From address, as well.

mdmonitor.c | 10 8 + 2 - 0 !
1 file changed, 8 insertions(+), 2 deletions(-)

 exit gracefully when md device not found (closes: #970329).

sha1.h | 8 4 + 4 - 0 !
1 file changed, 4 insertions(+), 4 deletions(-)

 do not #include ansidecl.h from sha1.h, use system headers.
 In 3.2.5 version of mdadm, new sha1 implementation has been included
 which tries to include ansidecl.h header which is internal to some
 other project. But this #include isn't really necessary, since this
 implementation does not actually use any defines from ansidecl.h. So
 just remove the #include, instead of adding a new external dependency.
 .
 References: http://www.spinics.net/lists/raid/msg38859.html
 .
 While at it, unconditionally include system headers like limits.h and
 stdint.h, since on a Linux system these headers are available, and
 these contains definitive information about real system types than
 any guesses.

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 remove -werror from compiler flags.
 -Werror seems like a bad idea on released/packaged code because a toolchain
 update (introducing new warnings) could break the build. We'll let upstream
 use it to beautify the code, but remove it for out builds.

tests/func.sh | 4 0 + 4 - 0 !
1 file changed, 4 deletions(-)

 test installed files (closes: #872118).
 The test suite seems to check the executable bit on the local build product
 'mdadm' but runs all programs from the system PATH. This change should test
 the installed version.
 .
 I believe this change tests the installed version, but that hypothesis is not
 supported by much else. The autopkgtest restriction isolation-machine made it

systemd/mdcheck_continue.timer | 4 3 + 1 - 0 !
systemd/mdcheck_start.timer | 2 2 + 0 - 0 !
systemd/mdmonitor-oneshot.service | 5 1 + 4 - 0 !
systemd/mdmonitor-oneshot.timer | 4 3 + 1 - 0 !
4 files changed, 9 insertions(+), 6 deletions(-)

 randomize md array check timers (lp: #1815201).

systemd/mdmonitor-oneshot.service | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 honor the debconf mdadm/autoscan setting in the systemd timer
 There was an mdadm/autoscan template added to allow users to disable this
 feature via debconf. This is exposed as a variable in /etc/default/mdadm,
 which was processed by a cronjob. Dropping the cronjob and moving to a
 systemd timer, we need to add our own processing.

systemd/mdcheck_continue.timer | 2 1 + 1 - 0 !
systemd/mdcheck_start.timer | 4 2 + 2 - 0 !
systemd/mdmonitor-oneshot.timer | 2 1 + 1 - 0 !
3 files changed, 4 insertions(+), 4 deletions(-)

 mdcheck fix empty spaces in timer unit files (lp: #1852747).
 dh_installsystemd is failling thus FBTFS because of the spaces
 in the systemd unit timer files directive.

Makefile | 6 5 + 1 - 0 !
1 file changed, 5 insertions(+), 1 deletion(-)

 patch makefile to use pkg-config systemd to discover systemd unit dir.

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 patch makefile to use /usr/sbin instead of /sbin.

mdadm.h | 2 1 + 1 - 0 !
mdopen.c | 30 6 + 24 - 0 !
util.c | 35 33 + 2 - 0 !
3 files changed, 40 insertions(+), 27 deletions(-)

 [patch] mdadm: load md_mod first

Load md_mod first before setting module parameter legacy_async_del_gendisk
Everything works well if md_mod is built in kernel. If not, create and
assemble will fail.

Fixes: d354d314db86 ("mdadm: Create array with sync del gendisk mode")
Signed-off-by: Xiao Ni <xni@redhat.com>

config.c | 25 24 + 1 - 0 !
mdadm.conf.5.in | 13 13 + 0 - 0 !
mdadm.h | 1 1 + 0 - 0 !
super-ddf.c | 2 1 + 1 - 0 !
4 files changed, 39 insertions(+), 2 deletions(-)

 [patch] mdadm.conf: add "probing ddf_extended" option

Add a configuration line PROBING to mdadm.conf. If the parameter
"ddf_extended" is set on this line, use the extended DDF header search
introduced by commit f2197b6b6c14 ("super-ddf: optimize DDF header search
for widely used RAID controllers"), at the cost of slower probing.
Otherwise, just check for the header in the last sector of the disk,
as usual.

Signed-off-by: Martin Wilck <mwilck@suse.com>