From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] MTD: at91: atmel_nand: for PMECC, add code to choose the ecc bits and sector size according to the ONFI parameter ECC requirement.
Date: Thu, 17 Jan 2013 13:54:35 +0200 [thread overview]
Message-ID: <1358423675.2731.232.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <50F664BC.7@atmel.com>
On Wed, 2013-01-16 at 16:28 +0800, Josh Wu wrote:
> Hi, Artem
>
> On 1/15/2013 8:26 PM, Artem Bityutskiy wrote:
> > I cannot compile this patch:
> >
> > ERROR (phandle_references): Reference to non-existent node or label "pinctrl_ssc0_tx"
> >
> > ERROR: Input tree has errors, aborting (use -f to force output)
> > make[2]: *** [arch/arm/boot/dts/at91sam9g20ek.dtb] Error 2
>
> As Bo Shen already mentioned, they are caused by ssc pinctrl patches. it
> will be merged in next rc or late.
Then ping me when the patches are ready to go, please.
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130117/18bb67c3/attachment.sig>
next prev parent reply other threads:[~2013-01-17 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 10:27 [PATCH 0/3] at91: PMECC: enable PMECC in dt for at91sam9x5ek, at91sam9n12ek Josh Wu
2012-12-19 10:27 ` [PATCH 1/3] MTD: at91: atmel_nand: for PMECC, add code to choose the ecc bits and sector size according to the ONFI parameter ECC requirement Josh Wu
2013-01-15 12:26 ` Artem Bityutskiy
2013-01-16 1:50 ` Bo Shen
2013-01-16 8:28 ` Josh Wu
2013-01-17 11:54 ` Artem Bityutskiy [this message]
2012-12-19 10:27 ` [PATCH 2/3] at91: 9x5: add DT parameters to enable PMECC Josh Wu
2012-12-19 10:27 ` [PATCH 3/3] at91: at91sam9n12: " Josh Wu
2013-01-14 9:01 ` [PATCH 0/3] at91: PMECC: enable PMECC in dt for at91sam9x5ek, at91sam9n12ek Josh Wu
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=1358423675.2731.232.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).