All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] dm: core: remove the duplicated function dm_ofnode_pre_reloc
Date: Mon, 4 Feb 2019 07:40:42 -0700	[thread overview]
Message-ID: <CAPnjgZ1DSdJ-o=51qLe8q2qjJo6vQu7n9qizzcmBJYtpopzaew@mail.gmail.com> (raw)
In-Reply-To: <1549275292-3134-2-git-send-email-patrick.delaunay@st.com>

Hi Patrick,

On Mon, 4 Feb 2019 at 03:15, Patrick Delaunay <patrick.delaunay@st.com> wrote:
>
> The content dm_ofnode_pre_reloc() is identical with ofnode_pre_reloc()
> defined in drivers/core/ofnode.c and used only one time
> in drivers/core/lists.c:lists_bind_fdt().
>
> So the function can be removed and directly call ofnode_pre_reloc.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
> ---
>
>  drivers/core/lists.c |  2 +-
>  drivers/core/util.c  | 26 --------------------------
>  include/dm/util.h    | 27 ---------------------------
>  3 files changed, 1 insertion(+), 54 deletions(-)

I think the docs for ofnode_pre_reloc() need updating.

Regards,
Simon

  reply	other threads:[~2019-02-04 14:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 10:14 [U-Boot] [PATCH 1/2] fdt: Allow indicating a node is for U-Boot proper only Patrick Delaunay
2019-02-04 10:14 ` [U-Boot] [PATCH 2/2] dm: core: remove the duplicated function dm_ofnode_pre_reloc Patrick Delaunay
2019-02-04 14:40   ` Simon Glass [this message]
2019-02-06  9:26     ` Patrick DELAUNAY
2019-02-04 14:40 ` [U-Boot] [PATCH 1/2] fdt: Allow indicating a node is for U-Boot proper only Simon Glass
2019-02-05  8:54   ` Marek Vasut
2019-02-07 17:40     ` Patrick DELAUNAY
2019-02-07 17:47       ` Marek Vasut
2019-02-08 12:47         ` Patrick DELAUNAY
2019-02-11 11:56         ` Patrick DELAUNAY
2019-02-11 11:58           ` Marek Vasut
2019-02-11 14:34             ` Patrick DELAUNAY
2019-05-18 16:20               ` Simon Glass
2019-05-20  7:41                 ` Patrick DELAUNAY

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='CAPnjgZ1DSdJ-o=51qLe8q2qjJo6vQu7n9qizzcmBJYtpopzaew@mail.gmail.com' \
    --to=sjg@chromium.org \
    --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.