From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 9/9] arm: Zap tricorder-eeprom
Date: Sat, 25 Oct 2014 01:25:33 +0200 [thread overview]
Message-ID: <201410250125.34022.marex@denx.de> (raw)
In-Reply-To: <20141024215836.15C0938018C@gemini.denx.de>
On Friday, October 24, 2014 at 11:58:36 PM, Wolfgang Denk wrote:
> Dear Marek,
>
> In message <1414006493-11461-10-git-send-email-marex@denx.de> you wrote:
> > This is a reimplementation of the cmd_eeprom with the added bit
> > where it can select I2C bus. Just remove this ugly duplication.
> > If someone needs this code, there should be proper implementation
> > submitted.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Andreas Bie?mann <andreas.biessmann@corscience.de>
> > Cc: Simon Glass <sjg@chromium.org>
> > Cc: Tom Rini <trini@ti.com>
> > Cc: Heiko Schocher <hs@denx.de>
> > ---
> >
> > board/corscience/tricorder/Makefile | 2 +-
> > board/corscience/tricorder/tricorder-eeprom.c | 251
> > --------------------------
> > board/corscience/tricorder/tricorder-eeprom.h | 41 -----
> > 3 files changed, 1 insertion(+), 293 deletions(-)
> > delete mode 100644 board/corscience/tricorder/tricorder-eeprom.c
> > delete mode 100644 board/corscience/tricorder/tricorder-eeprom.h
>
> Note that I'm _not_ applying this one. This is ARM, not PPC, so it
> should probably go through Albert's tree instead. An ACK from the
> board maintainer would also be nice?
Yeah, let's CC Andreas on his other email.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-10-24 23:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 19:34 [U-Boot] [PATCH 0/9] Pre-EEPROM cleanup series Marek Vasut
2014-10-22 19:34 ` [U-Boot] [PATCH 1/9] doc: Update README.scrapyard Marek Vasut
2014-10-22 21:45 ` Wolfgang Denk
2014-10-22 21:54 ` Marek Vasut
2014-10-24 21:35 ` Wolfgang Denk
2014-10-22 19:34 ` [U-Boot] [PATCH 2/9] ppc: Zap ICU862 board Marek Vasut
2014-10-24 21:47 ` Wolfgang Denk
2014-10-22 19:34 ` [U-Boot] [PATCH 3/9] ppc: Zap MHPC board Marek Vasut
2014-10-24 21:52 ` Wolfgang Denk
2014-10-22 19:34 ` [U-Boot] [PATCH 4/9] ppc: Zap Hymod board Marek Vasut
2014-10-24 21:54 ` Wolfgang Denk
2014-10-22 19:34 ` [U-Boot] [PATCH 5/9] ppc: Zap HWW1U1A board Marek Vasut
2014-10-24 21:54 ` Wolfgang Denk
2014-10-22 19:34 ` [U-Boot] [PATCH 6/9] ppc: Zap IDS8247 board Marek Vasut
2014-10-24 21:55 ` Wolfgang Denk
2014-10-22 19:34 ` [U-Boot] [PATCH 7/9] ppc: Zap TQM8260 board Marek Vasut
2014-10-24 21:55 ` Wolfgang Denk
2014-10-22 19:34 ` [U-Boot] [PATCH 8/9] ppc: Zap TQM8272 board Marek Vasut
2014-10-24 21:56 ` Wolfgang Denk
2014-10-22 19:34 ` [U-Boot] [PATCH 9/9] arm: Zap tricorder-eeprom Marek Vasut
2014-10-24 21:58 ` Wolfgang Denk
2014-10-24 23:25 ` Marek Vasut [this message]
2014-10-24 23:49 ` Andreas Bießmann
2014-10-24 23:52 ` Marek Vasut
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=201410250125.34022.marex@denx.de \
--to=marex@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