All of lore.kernel.org
 help / color / mirror / Atom feed
From: Levente Kurusa <lkurusa@redhat.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: "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 20:14:27 +0200	[thread overview]
Message-ID: <CAAsK9AGtdJiz0xnmfqLBAqxmt=r+WANsmxwB_vQ3O5aKzMW1LQ@mail.gmail.com> (raw)
In-Reply-To: <CAPDOMVjaf+vne4vbUPo8EPs0XnQBbNm2ZOXns8fw5pkg9tRSww@mail.gmail.com>

2014-07-22 19:40 GMT+02:00 Nick Krause <xerofoify@gmail.com>:
> [...]
>
> Tony,
>
> What is the value of Page shift then ? If you can tell me it would be
> much easier for
> me to fix this.
> Cheers Nick

Nick,

Help is always welcome. However, what you are doing is effectively a
waste of time for you and for the maintainers as well, and hence cannot
be called help. You are writing emails that make absolutely no sense at all.
If you want to help us out, please consider learning three things:

* The language that the kernel is written in: C
* The language that most kernel developers understand: English
* The environment the kernel is (in most cases) written in: UNIX

If you had known these, then:

* ... you would have already known that FIXMEs exist for a reason which is
   not at all simple.

* ... you would have understood that fixing FIXMEs without ANY reasoning and
   asking about it is completely useless and wastes precious maintainer time.

* ... you could have used grep for finding out PAGE_SHIFT and not need to ask
   for it.

Nick. Look, it is good that you are enthusiastic. However, this kind
of 'work' gives
you an undesirable reputation, which is {IF FROM:xerofoify@* THEN TRASH}...

If you really want to help out, I suggest you to find yourself a piece
of hardware from
the store and try to write a driver for it. That way, you will learn
how it all works, and if
you are intelligent enough then you might get a "Kernel Job - Payed"
like you asked us
for them in November.

Until then, please stop trying for FIXMEs. They will not get you a
commit in the kernel
99% of the time.

Hope you understand,

Levente Kurusa

  parent reply	other threads:[~2014-07-22 18:14 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 [this message]
2014-07-22 18:25         ` Nick Krause
2014-07-22 19:17           ` Randy Dunlap
2014-07-22 19:33           ` Steven Rostedt
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='CAAsK9AGtdJiz0xnmfqLBAqxmt=r+WANsmxwB_vQ3O5aKzMW1LQ@mail.gmail.com' \
    --to=lkurusa@redhat.com \
    --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=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.