From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-edac <linux-edac@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT PULL] EDAC updates for 4.
Date: Wed, 24 Jun 2015 14:30:48 +0200 [thread overview]
Message-ID: <20150624123047.GD32642@pd.tnic> (raw)
In-Reply-To: <CA+55aFwDRRZbRb2xp6t4W7TOtVkYQ7Xrq2+J5gBW4L3ufmzPHw@mail.gmail.com>
On Wed, Jun 24, 2015 at 05:14:34AM -0700, Linus Torvalds wrote:
> This shows such a fundamental misunderstanding of what you should send
> me that in starting to doubt all your other pull requests. How many of
> them worked by our luck? If you are not testing what you actually send
> me, I simply don't want to pull from you. It's that simple.
Ok, now this is really uncalled for.
I made the mistake of having the RAS x86 stuff going through tip - as it
always does - and have the drivers/edac/ changes in the EDAC tree.
But I have always merged the tip/x86/ras branch which contained the x86
changes into the EDAC tree when testing. Basically what I should've done
with the pull request too.
And dammit, I did test the hell of this thing. Like everything else I'm
testing. I'm trying to do my best but I can only try.
If there's anything I can do to stop you from doubting my pull requests,
please let me know.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-06-24 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 12:14 [GIT PULL] EDAC updates for 4 Linus Torvalds
2015-06-24 12:30 ` Borislav Petkov [this message]
2015-06-24 12:40 ` Linus Torvalds
2015-06-24 13:01 ` Linus Torvalds
2015-06-24 13:15 ` Borislav Petkov
2015-06-24 17:13 ` [GIT PULL] EDAC updates for 4.2 - v2 Borislav Petkov
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=20150624123047.GD32642@pd.tnic \
--to=bp@suse.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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