From: nick <xerofoify@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: What does oob stand for in mtd.h?
Date: Sat, 06 Dec 2014 20:43:33 -0500 [thread overview]
Message-ID: <5483B0C5.9080703@gmail.com> (raw)
In-Reply-To: <CAFLxGvyzcdwfNs6DJC4XT_yFH4yJBiqV_UV-JCavmcCeSdCd4w@mail.gmail.com>
Greetings Richard,
I do understand your concern and if you look at the logs for lkml, I have got two patches accepted into the mainline.
If there are any other ways I can prove that I am changed my attitude please let me known.
On 2014-12-06 05:55 AM, Richard Weinberger wrote:
> On Sat, Dec 6, 2014 at 4:58 AM, nick <xerofoify@gmail.com> wrote:
>> Greetings MTD subsystem developers,
>> I am wondering what oob stands for in mtd.h as a lot of functions are using it in their names. This would greatly need in me understanding the core of this subsystem if something points out what this stands for.
>> Regards and Thanks,
>> Nick
>
> BTW: I'll NACK every single patch from you which touches MTD until you
> prove that you have a setup to test
> your patches and completely changed your attitude.
>
> http://news.softpedia.com/news/Malevolent-Developer-Trolls-Linux-Kernel-Development-with-Lots-of-Broken-Patches-453709.shtml
>
next prev parent reply other threads:[~2014-12-07 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 3:58 What does oob stand for in mtd.h? nick
2014-12-06 6:36 ` Peter Barada
2014-12-06 10:55 ` Richard Weinberger
2014-12-07 1:43 ` nick [this message]
2014-12-07 10:36 ` Rafał Miłecki
2014-12-07 13:23 ` nick
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=5483B0C5.9080703@gmail.com \
--to=xerofoify@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@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.