From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-edac <linux-edac@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] A minor amd64_edac fix for 3.13
Date: Sat, 16 Nov 2013 11:29:47 +0100 [thread overview]
Message-ID: <20131116102947.GC18306@pd.tnic> (raw)
In-Reply-To: <CAADWXX_FdW4vGn8N4TA_GcNBrwuqeH_=qxmK2J7K7kfAWztxPA@mail.gmail.com>
And just to test whether you're getting emails from me, I'll send this
one again from my other mail address to try to maximize the probability
of some version actually reaching you :-)
On Fri, Nov 15, 2013 at 06:02:59PM -0800, Linus Torvalds wrote:
> [ This was in my spam collection. I don't quite know why, but it might
> signify problems with your email setup. Quite often, when gmail is
> unhappy about kernel developer emails, it's been because their email
> provider ends up doing something odd.
>
> But the headers actually have "spf=pass" and "dkim=pass", so it's
> nothing obvious. ]
Hmm, strange. Does this mean, you don't get other emails from my email
address or only this pull request? Say, do you have this one, for
example:
http://marc.info/?l=linux-kernel&m=138442829620489&w=2
where I ask you whether you're fine with Mauro and me playing interim
EDAC maintainers?
> That said, I don't much like the patch either. The "fixed' version
> looks worse than the original. If it's an unsigned type, no extra code
> will be generated,
Yes, correct, in both cases I have here:
.L779:
.loc 1 1579 0
cmpb $4, %r10b #, alias_channel
ja .L859 #,
.L847:
> and if it's a signed type, it's correct. In either way, the code looks
> good, and the range test means that people reading it don't even need
> to worry about whether the type is signed or not.
>
> If this patch was written because of some f*cking broken compiler
> warning, then just tell the compiler to shut the hell up about it.
> This is a clear example of where compiler warnings are actually making
> things worse.
Yeah, no, the compiler's fine here. Dave raised the issue about not
testing unsigned's for < 0:
http://www.spinics.net/lists/kernel/msg1597525.html
And I took it because it is less code in the .c source file to look at.
But I certainly don't care all that much whether the < 0 test is there
or not as long as the produced code is identical so...
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-11-16 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 12:26 [GIT PULL] A minor amd64_edac fix for 3.13 Borislav Petkov
2013-11-16 2:02 ` Linus Torvalds
2013-11-16 10:06 ` Borislav Petkov
[not found] ` <CA+55aFxHO9035t=CiNTRX1XK5KSxzh8HfZ3Kaspsm6yfs2O=8Q@mail.gmail.com>
2013-11-16 11:12 ` Borislav Petkov
2013-11-16 18:10 ` Linus Torvalds
2013-11-16 18:23 ` Borislav Petkov
2013-11-16 23:34 ` Frank Becker
[not found] ` <CA+55aFxZcNfOEadD7EixNf5YZJVLTJ=2T4TOybWfwTP71KnuRg@mail.gmail.com>
2013-11-17 1:22 ` Frank Becker
2013-11-17 7:47 ` Borislav Petkov
2013-11-16 10:29 ` Borislav Petkov [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=20131116102947.GC18306@pd.tnic \
--to=bp@suse.de \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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