public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Samuel Holland <samuel@sholland.org>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 3/3] remoteproc: Remove legacy probing method
Date: Thu, 30 Mar 2023 15:09:44 -0400	[thread overview]
Message-ID: <20230330190944.GA3606776@bill-the-cat> (raw)
In-Reply-To: <20230220061304.43198-4-samuel@sholland.org>

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

On Mon, Feb 20, 2023 at 12:13:03AM -0600, Samuel Holland wrote:

> This removes code that abused the device's platform data, interpreting
> the driver platform data as if it was the uclass platform data.
> 
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> Reviewed-by: Simon Glass <sjg@chromium.org>
> ---
> 
>  .../driver-model/remoteproc-framework.rst     | 29 -------------------
>  drivers/remoteproc/rproc-uclass.c             | 18 +-----------
>  drivers/remoteproc/sandbox_testproc.c         | 10 -------
>  include/remoteproc.h                          |  2 --
>  4 files changed, 1 insertion(+), 58 deletions(-)

This breaks the existing tests, please see
https://u-boot.readthedocs.io/en/latest/develop/ci_testing.html and/or
https://u-boot.readthedocs.io/en/latest/develop/py_testing.html for how
to run them.  Thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2023-03-30 19:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20  6:13 [PATCH 0/3] remoteproc: uclass cleanup Samuel Holland
2023-02-20  6:13 ` [PATCH 1/3] remoteproc: Move rproc_cfg_arr out of the uclass header Samuel Holland
2023-02-21 19:35   ` Simon Glass
2023-02-20  6:13 ` [PATCH 2/3] remoteproc: Remove unused mem_type platform data Samuel Holland
2023-02-20 16:21   ` Simon Glass
2023-02-20 16:54   ` Tom Rini
2023-02-20  6:13 ` [PATCH 3/3] remoteproc: Remove legacy probing method Samuel Holland
2023-02-21 19:35   ` Simon Glass
2023-03-30 19:09   ` Tom Rini [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=20230330190944.GA3606776@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=samuel@sholland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox