From: nick <xerofoify@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>, "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>, Jonas Gorski <jogo@openwrt.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: [RFC] ARM: BCM5301X: add NAND flash chip description
Date: Tue, 26 May 2015 16:53:11 -0400 [thread overview]
Message-ID: <5564DD37.1090506@gmail.com> (raw)
In-Reply-To: <CACna6rxOBnxeNFP3ogxVyB+F_BeMN9mGq6vM+zUQeRqsz1cJuQ@mail.gmail.com>
On 2015-05-26 04:20 PM, Rafał Miłecki wrote:
> On 24 May 2015 at 20:32, Hauke Mehrtens <hauke@hauke-m.de> wrote:
>> This adds the NAND flash chip description for a standard chip found
>> connected to this SoC. This makes use of generic Broadcom NAND driver
>> with the iProc interface.
>
> I still wait/hope for Brian's reply in
> [PATCH 5/7] mtd: brcmnand: add bcma driver
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
Rafal,
How long has it been as if its over a week I would like resend the patch.
Nick
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2015-05-26 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 18:32 [RFC] ARM: BCM5301X: add NAND flash chip description Hauke Mehrtens
[not found] ` <1432492349-18517-1-git-send-email-hauke-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2015-05-26 20:20 ` Rafał Miłecki
2015-05-26 20:53 ` nick [this message]
2015-05-27 0:41 ` Brian Norris
2015-05-27 1:15 ` Brian Norris
2015-05-27 22:04 ` Hauke Mehrtens
2015-05-27 7:37 ` Arnd Bergmann
2015-05-27 21:46 ` Hauke Mehrtens
[not found] ` <55663B48.5060306-5/S+JYg5SzeELgA04lAiVw@public.gmane.org>
2015-05-27 21:57 ` Brian Norris
2015-05-28 8:21 ` Arnd Bergmann
2015-05-29 15:29 ` Hauke Mehrtens
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=5564DD37.1090506@gmail.com \
--to=xerofoify@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jogo@openwrt.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rjui@broadcom.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;
as well as URLs for NNTP newsgroup(s).