From: Gaston Gonzalez <gascoar@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Adrien Thierry <athierry@redhat.com>,
bcm-kernel-feedback-list@broadcom.com,
Florian Fainelli <f.fainelli@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, gascoar@gmail.com
Subject: Re: [PATCH v2 0/9] staging: vchiq_arm: remove some unnecessary global variables
Date: Wed, 1 Jun 2022 19:12:28 -0300 [thread overview]
Message-ID: <20220601221228.cffvvnwm37b7q3xf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <e9d2cf9a-c4f0-997f-72f5-1b10379dc126@i2se.com>
On Mon, May 30, 2022 at 10:19:14PM +0200, Stefan Wahren wrote:
> Hi Adrien,
>
> Am 18.05.22 um 21:11 schrieb Adrien Thierry:
> > This patch series aims at removing some unnecessary global structures
> > (namely, 'g_dev' and 'vchiq_states'), in order to make the driver more
> > robust. This is part of an effort to address TODO item "Get rid of all non
> > essential global structures and create a proper per device structure".
>
> sorry for the delay, but i was fighting with some platform regressions in
> Linux 5.18.
>
> So except of my comments, this series is:
>
> Tested-by: Stefan Wahren <stefan.wahren@i2se.com>
>
>
Hi Stefan,
Not directly related to these patches, but if you don't mind I would
like to know what tests in specific are necessary to tag a Tested-by on
a vchiq patch?
For instance, running the userland vchiq_test -f on a RPi 3B would be
enough?
thanks,
Gaston
prev parent reply other threads:[~2022-06-01 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 19:11 [PATCH v2 0/9] staging: vchiq_arm: remove some unnecessary global variables Adrien Thierry
2022-05-18 19:11 ` [PATCH v2 1/9] staging: vchiq_arm: add reference to vchiq device in vchiq_state Adrien Thierry
2022-05-18 19:11 ` [PATCH v2 2/9] staging: vchiq_arm: get rid of global device structure Adrien Thierry
2022-05-18 19:11 ` [PATCH v2 3/9] staging: vchiq_arm: pass vchiq instance to service callbacks Adrien Thierry
2022-05-30 19:26 ` Stefan Wahren
2022-05-18 19:11 ` [PATCH v2 4/9] staging: vchiq_arm: pass vchiq instance to 'find_service_by_handle' Adrien Thierry
2022-05-30 19:43 ` Stefan Wahren
2022-05-18 19:11 ` [PATCH v2 5/9] staging: vchiq_arm: pass vchiq instance to 'vchiq_get_client_id' Adrien Thierry
2022-05-18 19:11 ` [PATCH v2 6/9] staging: vchiq_arm: pass vchiq instance to 'vchiq_get_service_userdata' Adrien Thierry
2022-05-18 19:11 ` [PATCH v2 7/9] staging: vchiq_arm: pass vchiq instance to 'handle_to_service' Adrien Thierry
2022-05-18 19:11 ` [PATCH v2 8/9] staging: vchiq_arm: use state from vchiq instance Adrien Thierry
2022-05-30 20:09 ` Stefan Wahren
2022-05-18 19:11 ` [PATCH v2 9/9] staging: vchiq_arm: remove global 'vchiq_states' array Adrien Thierry
2022-05-30 20:19 ` [PATCH v2 0/9] staging: vchiq_arm: remove some unnecessary global variables Stefan Wahren
2022-06-01 22:12 ` Gaston Gonzalez [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=20220601221228.cffvvnwm37b7q3xf@debian-BULLSEYE-live-builder-AMD64 \
--to=gascoar@gmail.com \
--cc=athierry@redhat.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=nsaenz@kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
/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;
as well as URLs for NNTP newsgroup(s).