linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: "Paweł Sikora" <pluto@agmk.net>, linux-raid@vger.kernel.org
Subject: Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
Date: Tue, 15 May 2012 07:32:19 +1000	[thread overview]
Message-ID: <20120515073219.1275b10a@notabene.brown> (raw)
In-Reply-To: <4FB17212.3000308@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]

On Mon, 14 May 2012 22:58:58 +0200 Jes Sorensen <Jes.Sorensen@redhat.com>
wrote:

> On 05/14/12 22:57, Paweł Sikora wrote:
> > On Monday 14 of May 2012 22:30:32 Jes Sorensen wrote:
> >> On 05/12/12 08:36, Paweł Sikora wrote:
> >>> fyi, this release contains a hidden strict-aliasing-violation bug [1].
> >>> please fix this correctly or build mdadm with -fno-strict-aliasing option.
> >>>
> >>> [1] http://www.spinics.net/lists/raid/msg37298.html
> >>
> >> If you provide a patch, you're more likely to get the issue fixed than
> >> by just telling other people to fix it for you.
> > 
> > i have sent you a revert request with a proper fix 3 months ago
> > and you have finally rejected it with "invalid commit message",
> > so feel free to keep broken mdadm sources as long as you wish :>
> > 
> 
> If you post a patch without including a proper commit message and
> signed-off-by lines, which is standard practice, then that is equivalent
> to you not having posted a patch in the first place.
> 
> Don't blame others for not doing the basic work everybody else does when
> posting patches. It really isn't hard to comply with the standard patch
> posting rules!

I decided a better approach is just to refresh from upstream:

      http://gcc.gnu.org/svn/gcc/branches/cilkplus/include/sha1.h
      http://gcc.gnu.org/svn/gcc/branches/cilkplus/libiberty/sha1.c

have been copied into mdadm with just a tiny change to not include config.h

Seems to work, and probably has the *right* fix.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-05-14 21:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12  6:36 ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux Paweł Sikora
2012-05-14 20:30 ` Jes Sorensen
2012-05-14 20:57   ` Paweł Sikora
2012-05-14 20:58     ` Jes Sorensen
2012-05-14 21:32       ` NeilBrown [this message]
2012-05-15  7:03         ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2012-05-09  1:29 NeilBrown
2012-05-10 14:59 ` Jes Sorensen

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=20120515073219.1275b10a@notabene.brown \
    --to=neilb@suse.de \
    --cc=Jes.Sorensen@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=pluto@agmk.net \
    /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).