From: nick <xerofoify@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: What does oob stand for in mtd.h?
Date: Sun, 07 Dec 2014 08:23:38 -0500 [thread overview]
Message-ID: <548454DA.9060902@gmail.com> (raw)
In-Reply-To: <CACna6rxHgwa8A+om-yhcGU9gr+RjauqJu_SpTuUn1_sY+OqNQA@mail.gmail.com>
Rafal,
Clearly you did not read the logs more carefully. My patch was accepted for x86 kvm subsystem.
Regards Nick
On 2014-12-07 05:36 AM, Rafał Miłecki wrote:
> On 7 December 2014 at 02:43, nick <xerofoify@gmail.com> wrote:
>> 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.
>
> Your reputation seems to be known for months and only recently you
> tried to fool us (me) with your b43 patch
> [PATCH] drivers:net:wireless: Add mutex locking for function,
> b43_op_beacon_set_time in main.c
>
> I don't think anything has changed in the last 9 days (since b43 patch).
>
prev parent reply other threads:[~2014-12-07 13:24 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
2014-12-07 10:36 ` Rafał Miłecki
2014-12-07 13:23 ` nick [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=548454DA.9060902@gmail.com \
--to=xerofoify@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=zajec5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox