From: Sourav Poddar <sourav.poddar@ti.com>
To: Huang Shijie <b32955@freescale.com>
Cc: marex@denx.de, computersforpeace@gmail.com,
linux-mtd@lists.infradead.org, balbi@ti.com, dedekind1@gmail.com
Subject: Re: [PATCHv2] drivers: mtd: m25p80: Add quad read support.
Date: Wed, 30 Oct 2013 14:11:40 +0530 [thread overview]
Message-ID: <5270C644.1020405@ti.com> (raw)
In-Reply-To: <5270BC27.40000@freescale.com>
On Wednesday 30 October 2013 01:28 PM, Huang Shijie wrote:
> 于 2013年10月30日 15:22, Sourav Poddar 写道:
>> struct device_node __maybe_unused *np = spi->dev.of_node;
> you'd better rebase this patch on the latest l2-mtd.
>
> this line has been removed in the latest code.
>
Ok.
>
> thanks
> Huang Shijie
>
prev parent reply other threads:[~2013-10-30 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 7:22 [PATCHv2] drivers: mtd: m25p80: Add quad read support Sourav Poddar
2013-10-30 7:58 ` Huang Shijie
2013-10-30 8:41 ` Sourav Poddar [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=5270C644.1020405@ti.com \
--to=sourav.poddar@ti.com \
--cc=b32955@freescale.com \
--cc=balbi@ti.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
/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).