From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 01/25] ppc: Zap ICU862 board
Date: Wed, 22 Oct 2014 21:10:28 +0200 [thread overview]
Message-ID: <201410222110.28867.marex@denx.de> (raw)
In-Reply-To: <20141020185529.A4F673833B9@gemini.denx.de>
On Monday, October 20, 2014 at 08:55:29 PM, Wolfgang Denk wrote:
> Dear Marek,
>
> In message <201410201649.49448.marex@denx.de> you wrote:
> > Ah, you're right, we have this thing. One thing I'm not sure about is how
> > is someone supposed to determine the commit in which the board was
> > removed before the commit was created in the upstream repository. This
> > kinda doesn't add up to me.
>
> You just insert place holders for the boards you are touching, and fix
> up older entries that already hit mainline.
I wonder if we shouldn't get rid of this README.scrapyard. Personally, I
don't find much value in it to be honest ; if I am looking for some ancient
board, I just do git log -p and search for whatever I need.
That said, I will fix up the patches ... also, I will split the removal
from the eeprom changes, so the removal doesn't block the eeprom stuff.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-10-22 19:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 1:48 [U-Boot] [RFC][PATCH 00/25] eeprom: Cleanup and support for multiple i2c busses Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 01/25] ppc: Zap ICU862 board Marek Vasut
2014-10-20 3:54 ` Masahiro Yamada
2014-10-20 14:49 ` Marek Vasut
2014-10-20 18:55 ` Wolfgang Denk
2014-10-22 19:10 ` Marek Vasut [this message]
2014-10-23 2:26 ` Masahiro Yamada
2014-10-24 14:37 ` Marek Vasut
2014-10-20 19:07 ` Wolfgang Denk
2014-10-20 1:48 ` [U-Boot] [PATCH 02/25] ppc: Zap MHPC board Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 03/25] ppc: Zap Hymod board Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 04/25] ppc: Zap HWW1U1A board Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 05/25] ppc: Zap IDS8247 board Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 06/25] ppc: Zap TQM8260 board Marek Vasut
2014-10-20 19:08 ` Wolfgang Denk
2014-10-20 1:48 ` [U-Boot] [PATCH 07/25] ppc: Zap TQM8272 board Marek Vasut
2014-10-20 19:08 ` Wolfgang Denk
2014-10-20 1:48 ` [U-Boot] [PATCH 08/25] arm: Zap tricorder-eeprom Marek Vasut
2014-11-04 16:01 ` [U-Boot] [RFC PATCH] tricorder: rewrite tricordereeprom command Andreas Bießmann
2015-11-10 19:10 ` Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 09/25] eeprom: Shuffle code around Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 10/25] eeprom: Zap CONFIG_SYS_I2C_MULTI_EEPROMS Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 11/25] eeprom: Zap CONFIG_SYS_EEPROM_X40430 Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 12/25] eeprom: Zap eeprom_probe() Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 13/25] eeprom: Zap CONFIG_SPI_X Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 14/25] eeprom: Pull out the I/O code Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 15/25] eeprom: Pull out address computation Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 16/25] eeprom: Make eeprom_write_enable() weak Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 17/25] eeprom: Pull out CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 18/25] eeprom: Suck the ifdef into eeprom_init() Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 19/25] eeprom: Pull out CONFIG_SYS_EEPROM_PAGE_WRITE_BITS Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 20/25] eeprom: Pull out transfer length computation Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 21/25] eeprom: Pull out the RW loop Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 22/25] eeprom: Cultivate the ifdef mess Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 23/25] eeprom: Add bus argument to eeprom_init() Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 24/25] eeprom: Add support for selecting i2c bus Marek Vasut
2014-10-20 1:48 ` [U-Boot] [PATCH 25/25] eeprom: Clean up checkpatch issues 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=201410222110.28867.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