On 17/07/2013 11:10, Albert ARIBAUD wrote:
Hi Stefano,
On Wed, 17 Jul 2013 10:04:29 +0200, Stefano Babic sbabic@denx.de wrote:
Hi Albert,
On 17/07/2013 09:42, Albert ARIBAUD wrote:
Hi Fabio,
On Mon, 15 Jul 2013 14:29:28 -0300, Fabio Estevam fabio.estevam@freescale.com wrote:
mx6qsabrelite and nitrogen6q boards are hardware compatible, so let's avoid the code duplication and only use the nitrogen6x source code to make board code maintainance easier.
Tested booting a mainline device tree kernel on a mx6qsabrelite board.
Signed-off-by: Fabio Estevam fabio.estevam@freescale.com
Hmm, why does this patch not show on Patchwork? Only its V1 does.
I am struggling for finding it, too. I have already seen a similar case in the past. Otavio remarked that when there is a rename, patchwork is not able to track it (bug in patchwork).
Since we have a clear example (and on the patchwork site where the patchwork folks can dig as deep as they need), we could bring this up to the patchwork list, with the M-IDs of the V1 and V2 patches.
A second example was :
[PATCH 5/6] mx28evk: Move README file inside board directory
This can be found in the ML, but I never found it in patchworks. This patch renamed only a file:
diff --git a/doc/README.mx28evk b/board/freescale/mx28evk/README similarity index 100% rename from doc/README.mx28evk rename to board/freescale/mx28evk/README
For this reason the disappearing of mx6qsabrelite can be related, because also this patch renames a file.
Regards, Stefano