From: Steven Rostedt <rostedt@goodmis.org>
To: Nick Krause <xerofoify@gmail.com>
Cc: "Levente Kurusa" <lkurusa@redhat.com>,
"Tony Luck" <tony.luck@gmail.com>, "Bjørn Mork" <bjorn@mork.no>,
"Doug Thompson" <dougthompson@xmission.com>,
"Borislav Petkov" <bp@alien8.de>,
"m.chehab@samsung.com" <m.chehab@samsung.com>,
"Linux Edac Mailing List" <linux-edac@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] edac: Remove fixmes in e7xxx_edac.c
Date: Tue, 22 Jul 2014 15:33:50 -0400 [thread overview]
Message-ID: <20140722193350.GA486@home.goodmis.org> (raw)
In-Reply-To: <CAPDOMVhj72TFKbtw_93juX19WVdfUzh3KM9tCEjbTdUZvUfcUQ@mail.gmail.com>
On Tue, Jul 22, 2014 at 02:25:24PM -0400, Nick Krause wrote:
>
> I understand what your saying and I should have searched for Page shift.
> In addition I am already got commits in the kernel for fix mes so I feel
> that your comment on fix mes is incorrect.
After seeing your other solutions to "fix mes" around the kernel, I now have to
investigate the patches that were accepted, and see if they did not cause
any new bugs. If any of them do, I will ask to have all your patches reverted.
You are not helping. You are actually doing quite the opposite. Who do you work
for? Microsoft or Apple?
-- Steve
next prev parent reply other threads:[~2014-07-22 19:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 4:53 [PATCH] edac: Remove fixmes in e7xxx_edac.c Nicholas Krause
2014-07-22 14:04 ` Bjørn Mork
2014-07-22 17:25 ` Tony Luck
2014-07-22 17:40 ` Nick Krause
2014-07-22 17:46 ` Borislav Petkov
2014-07-22 18:03 ` Nick Krause
2014-07-22 18:08 ` Borislav Petkov
2014-07-22 18:14 ` Levente Kurusa
2014-07-22 18:25 ` Nick Krause
2014-07-22 19:17 ` Randy Dunlap
2014-07-22 19:33 ` Steven Rostedt [this message]
2014-07-22 20:56 ` Nick Krause
2014-07-23 14:37 ` Steven Rostedt
2014-07-23 15:35 ` Nick Krause
2014-07-23 16:07 ` Steven Rostedt
2014-07-23 16:19 ` Nick Krause
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=20140722193350.GA486@home.goodmis.org \
--to=rostedt@goodmis.org \
--cc=bjorn@mork.no \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkurusa@redhat.com \
--cc=m.chehab@samsung.com \
--cc=tony.luck@gmail.com \
--cc=xerofoify@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.