From: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
To: "richard.weinberger@gmail.com" <richard.weinberger@gmail.com>
Cc: "richard@nod.at" <richard@nod.at>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: Two lame typo fixes
Date: Tue, 30 Sep 2014 06:31:50 +0000 [thread overview]
Message-ID: <1412058710.3904.0.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAFLxGvyFdpSEiOqVGyGWoeqzMK_jRUrRWbHL8SvySU+bPjj57A@mail.gmail.com>
On Tue, 2014-09-30 at 00:24 +0200, Richard Weinberger wrote:
> On Tue, Sep 16, 2014 at 3:30 PM, Richard Weinberger <richard@nod.at> wrote:
> > ...found them while browsing.
> >
> > Thanks,
> > //richard
> >
> > [PATCH 1/2] UBI: Fix trivial typo in __schedule_ubi_work
> > [PATCH 2/2] UBIFS: Fix trivial typo in power_cut_emulated()
>
> ping?
Pushed both, thanks!
--
Best Regards,
Artem Bityutskiy
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
prev parent reply other threads:[~2014-09-30 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 13:30 Two lame typo fixes Richard Weinberger
2014-09-16 13:30 ` [PATCH 1/2] UBI: Fix trivial typo in __schedule_ubi_work Richard Weinberger
2014-09-16 13:30 ` [PATCH 2/2] UBIFS: Fix trivial typo in power_cut_emulated() Richard Weinberger
2014-09-29 22:24 ` Two lame typo fixes Richard Weinberger
2014-09-30 6:31 ` Bityutskiy, Artem [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=1412058710.3904.0.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@intel.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).