From: Huang Shijie <b32955@freescale.com>
To: <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Peter Rusko <rusko.peter@prolan.hu>,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: linux/mtd/gpmi-nand.h: No such file or directory
Date: Mon, 16 Jan 2012 19:34:48 +0800 [thread overview]
Message-ID: <4F140B58.5080401@freescale.com> (raw)
In-Reply-To: <1326713359.14299.59.camel@sauron.fi.intel.com>
Hi,
>> Shawn has added it to his git tree to fix the compiling error.
> This issue is upstream for long time, when are you planning to submit
> this patch? Can you send it now and I'll ask David to merge it - there
to Shawn:
When does your git tree been merged? Should I sent a patch to fix it?
Huang Shijie
> is anyway another patch which requires quick merging upstream.
>
next prev parent reply other threads:[~2012-01-16 11:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 11:22 linux/mtd/gpmi-nand.h: No such file or directory Peter Rusko
2012-01-16 11:21 ` Artem Bityutskiy
2012-01-16 11:26 ` Huang Shijie
2012-01-16 11:29 ` Artem Bityutskiy
2012-01-16 11:34 ` Huang Shijie [this message]
2012-01-16 11:37 ` Artem Bityutskiy
2012-01-16 12:32 ` Shawn Guo
2012-01-16 12:25 ` Artem Bityutskiy
2012-01-16 12:31 ` Koul, Vinod
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=4F140B58.5080401@freescale.com \
--to=b32955@freescale.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rusko.peter@prolan.hu \
--cc=shawn.guo@freescale.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.