From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] mx6: Remove duplication of iomuxc structure
Date: Wed, 23 Jul 2014 12:36:32 +0200 [thread overview]
Message-ID: <53CF9030.8090705@denx.de> (raw)
In-Reply-To: <1404939595-16151-1-git-send-email-festevam@gmail.com>
On 09/07/2014 22:59, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> There is no need to keep iomuxc_base_regs structure as it serves the exact same
> purpose of the iomuxc structure, which is to provide access to the GPR
> registers.
>
> The additional fields of iomuxc_base_regs are not used. Other advantage of
> 'iomuxc' is that it has a shorter name and the variable declarations can fit
> into a single line.
>
> So remove iomuxc_base_regs structure and use iomuxc instead.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
Applied to u-boot-imx, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
prev parent reply other threads:[~2014-07-23 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 20:59 [U-Boot] [PATCH 1/2] mx6: Remove duplication of iomuxc structure Fabio Estevam
2014-07-09 20:59 ` [U-Boot] [PATCH 2/2] mx6: Adjust the GPR offset for mx6solox Fabio Estevam
2014-07-11 7:42 ` Stefano Babic
2014-07-23 10:36 ` Stefano Babic
2014-07-11 7:41 ` [U-Boot] [PATCH 1/2] mx6: Remove duplication of iomuxc structure Stefano Babic
2014-07-23 10:36 ` Stefano Babic [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=53CF9030.8090705@denx.de \
--to=sbabic@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.