From: "Brian Norris" <norris@broadcom.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: "pjohn@mvista.com" <pjohn@mvista.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd-www doc, FAQ, general: spelling fixes
Date: Thu, 8 Jul 2010 15:23:36 -0700 [thread overview]
Message-ID: <4C364FE8.1030101@broadcom.com> (raw)
In-Reply-To: <1278581058.12733.77.camel@localhost>
>
> Pushed, thanks a lot!
>
I think you missed the first patch :) I'm not sure it applies properly
now, but here's the link. I can reformat it if necessary:
http://lists.infradead.org/pipermail/linux-mtd/2010-June/030705.html
next prev parent reply other threads:[~2010-07-08 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 22:42 [PATCH] mtd-www doc, FAQ, general: spelling fixes Brian Norris
2010-06-24 13:52 ` Philby John
2010-06-24 16:41 ` Brian Norris
2010-07-08 9:24 ` Artem Bityutskiy
2010-07-08 22:23 ` Brian Norris [this message]
2010-07-18 7:24 ` Artem Bityutskiy
2010-07-13 8:10 ` Artem Bityutskiy
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=4C364FE8.1030101@broadcom.com \
--to=norris@broadcom.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pjohn@mvista.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;
as well as URLs for NNTP newsgroup(s).