public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/6 V4] I2C: Driver changes for FDT support
Date: Thu, 29 Nov 2012 09:33:21 +0100	[thread overview]
Message-ID: <50B71DD1.5000804@denx.de> (raw)
In-Reply-To: <1354172991-1005-6-git-send-email-rajeshwari.s@samsung.com>

Hello Rajeshwari,

On 29.11.2012 08:09, Rajeshwari Shinde wrote:
> Functions added to get the I2C bus number and reset I2C bus using
> FDT node.
>
> Signed-off-by: Rajeshwari Shinde<rajeshwari.s@samsung.com>
> Acked-by: Simon Glass<sjg@chromium.org>

Nitpick: missing my Acked by ... so here it comes again:

Acked-by: Heiko Schocher <hs@denx.de>

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2012-11-29  8:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29  7:09 [U-Boot] [PATCH 0/6 V4] EXYNOS5: FDT Support for I2C Rajeshwari Shinde
2012-11-29  7:09 ` [U-Boot] [PATCH 1/6 V4] EXYNOS5: FDT: Add I2C device node data Rajeshwari Shinde
2012-11-29  7:09 ` [U-Boot] [PATCH 2/6 V4] EXYNOS5 : FDT: Add Aliases for I2C device Rajeshwari Shinde
2012-11-29  7:09 ` [U-Boot] [PATCH 3/6 V4] EXYNOS5: FDT: Add compatible string for I2C Rajeshwari Shinde
2012-11-29  7:09 ` [U-Boot] [PATCH 4/6 V4] EXYNOS5: FDT : Decode peripheral id Rajeshwari Shinde
2012-11-30  4:56   ` Simon Glass
2012-11-29  7:09 ` [U-Boot] [PATCH 5/6 V4] I2C: Driver changes for FDT support Rajeshwari Shinde
2012-11-29  8:33   ` Heiko Schocher [this message]
2012-11-29  9:26     ` Rajeshwari Birje
     [not found]       ` <CAJZ5Ok2THcLsR4xyzf2HSO_vDVW6wfb40F3DJ-z96rY=wNgecQ@mail.gmail.com>
2012-12-03  5:52         ` Rajeshwari Birje
2012-11-29  7:09 ` [U-Boot] [PATCH 6/6 V4] SMDK5250: Initialise I2C using FDT Rajeshwari Shinde
2012-11-29  8:16 ` [U-Boot] [PATCH 0/6 V4] EXYNOS5: FDT Support for I2C Rajeshwari Birje

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=50B71DD1.5000804@denx.de \
    --to=hs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox