U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/4] arm: socfpga: clean up socfpga_common.h
Date: Wed, 24 Apr 2019 19:42:07 +0200	[thread overview]
Message-ID: <e539f406-d137-626d-57d4-1bebeb360cf4@denx.de> (raw)
In-Reply-To: <a136bbd4-34d4-7947-4872-0de94ea928ac@gmail.com>

On 4/24/19 7:36 PM, Simon Goldschmidt wrote:
> Am 23.04.2019 um 23:24 schrieb Marek Vasut:
>> On 4/23/19 10:51 PM, Simon Goldschmidt wrote:
>>>
>>>
>>> Marek Vasut <marex at denx.de <mailto:marex@denx.de>> schrieb am Di., 23.
>>> Apr. 2019, 22:43:
>>>
>>>      On 4/23/19 9:36 PM, Simon Goldschmidt wrote:
>>>      > This series cleans up the include/configs/socfpga_common.h
>>> file a bit.
>>>      >
>>>      > It removes some defines that are used nowhere and cleans up some
>>>      > leftovers after various subsystems have been converted to use DM.
>>>      >
>>>      > Changes in v4:
>>>      > - fix DM_I2C case: don't call i2c_set_bus_num() since this is
>>>      >   done in cmd/eeprom already
>>>      >
>>>      > Changes in v3:
>>>      > - changed commit message: s/defines/macros and comments/
>>>      >
>>>      > Changes in v2:
>>>      > - added (this) patch to move socfpga_vining to DM_I2C
>>>      > - remove even more outdated things
>>>      > - added (this) patch with further cleanups to the socfpga
>>> board config
>>>      >   files
>>>      >
>>>      > Simon Goldschmidt (4):
>>>      >   arm: socfpga: move vining_fpga to DM_I2C
>>>      >   arm: socfpga: clean up socfpga_common.h
>>>      >   arm: socfpga: remove CONFIG_SYS_BOOTMAPSZ
>>>      >   arm: socfpga: clean up board config files
>>>      >
>>>      >  board/samtec/vining_fpga/socfpga.c       |  9 +---
>>>      >  configs/socfpga_vining_fpga_defconfig    |  8 ++-
>>>      >  include/configs/socfpga_arria10_socdk.h  |  6 ---
>>>      >  include/configs/socfpga_arria5_socdk.h   |  2 -
>>>      >  include/configs/socfpga_common.h         | 68
>>>      ------------------------
>>>      >  include/configs/socfpga_cyclone5_socdk.h |  2 -
>>>      >  include/configs/socfpga_de0_nano_soc.h   |  2 -
>>>      >  include/configs/socfpga_de10_nano.h      |  2 -
>>>      >  include/configs/socfpga_de1_soc.h        |  2 -
>>>      >  include/configs/socfpga_is1.h            |  2 -
>>>      >  include/configs/socfpga_sockit.h         |  2 -
>>>      >  include/configs/socfpga_socrates.h       |  2 -
>>>      >  include/configs/socfpga_sr1500.h         | 11 ----
>>>      >  include/configs/socfpga_vining_fpga.h    | 18 -------
>>>      >  14 files changed, 8 insertions(+), 128 deletions(-)
>>>
>>>      Neither of these apply to u-boot-socfpga/master :-(
>>>
>>>
>>> Sorry for the confusion, these are again meant to apply on top of other
>>> patches in a PR. Sent to the ML for reference, mainly, as the diffs are
>>> tiny.
>>>
>>> How should I mark such patches to prevent such misunderstandings in the
>>> future?
>>
>> Just send an incremental patch on top of u-boot-socfpga/master please .
>> If you want me to squash it into another patch, note it somewhere around
>> the diffstat.
>>
> 
> OK, in this case, drop this v4.

Cool, thanks.

-- 
Best regards,
Marek Vasut

      reply	other threads:[~2019-04-24 17:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 19:36 [U-Boot] [PATCH v4 0/4] arm: socfpga: clean up socfpga_common.h Simon Goldschmidt
2019-04-23 19:36 ` [U-Boot] [PATCH v4 1/4] arm: socfpga: move vining_fpga to DM_I2C Simon Goldschmidt
2019-04-23 19:36 ` [U-Boot] [PATCH v4 2/4] arm: socfpga: clean up socfpga_common.h Simon Goldschmidt
2019-04-23 19:36 ` [U-Boot] [PATCH v4 3/4] arm: socfpga: remove CONFIG_SYS_BOOTMAPSZ Simon Goldschmidt
2019-04-23 19:36 ` [U-Boot] [PATCH v4 4/4] arm: socfpga: clean up board config files Simon Goldschmidt
2019-04-23 20:43 ` [U-Boot] [PATCH v4 0/4] arm: socfpga: clean up socfpga_common.h Marek Vasut
2019-04-23 20:51   ` Simon Goldschmidt
2019-04-23 21:24     ` Marek Vasut
2019-04-24 17:36       ` Simon Goldschmidt
2019-04-24 17:42         ` Marek Vasut [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=e539f406-d137-626d-57d4-1bebeb360cf4@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