From: Angelo Dureghello <sysamfw@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] patches status
Date: Thu, 10 Jan 2013 10:53:37 +0100 [thread overview]
Message-ID: <20130110095337.GA4659@sion.sysam> (raw)
Dear All,
sorry if i ask, don't want to put any pressure.
I am currently blocked to port a new board patch on the list, depending on
two patches i posted in november:
[U-Boot,1/1] m68k/lib: fix serial driver relocation
http://patchwork.ozlabs.org/patch/201421/
[U-Boot,1/1] mtd/cfi: add support for SST 4KB sector granularity
http://patchwork.ozlabs.org/patch/203086/
The first one is related tho serial routines erroneously running from flash.
This is important for me to be accepted to proceed with the board patch, but
the issues affects currently all coldfire boards.
The second is less important, i can write my own flash.c, but would be nice
to know if there is any chance it can eb accepted.
Regards,
Angelo Dureghello
Dear All,
sorry if i ask, don't want to put any pressure.
I am currently blocked to port a new board patch on the list, depending on
two patches i posted in november:
[U-Boot,1/1] m68k/lib: fix serial driver relocation
http://patchwork.ozlabs.org/patch/201421/
[U-Boot,1/1] mtd/cfi: add support for SST 4KB sector granularity
http://patchwork.ozlabs.org/patch/203086/
The first one is related tho serial routines erroneously running from flash.
This is important for me to be accepted to proceed with the board patch, but
the issues affects currently all coldfire boards.
The second is less important, i can write my own flash.c, but would be nice
to know if there is any chance it can eb accepted.
Regards,
Angelo Dureghello
next reply other threads:[~2013-01-10 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 9:53 Angelo Dureghello [this message]
2013-01-10 12:12 ` [U-Boot] patches status Stefan Roese
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=20130110095337.GA4659@sion.sysam \
--to=sysamfw@gmail.com \
--cc=u-boot@lists.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