From: Stefan Wahren <stefan.wahren@i2se.com>
To: Ojaswin Mujoo <ojaswin98@gmail.com>,
nsaenz@kernel.org, gregkh@linuxfoundation.org
Cc: dan.carpenter@oracle.com, phil@raspberrypi.com,
linux-arm-kernel@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] staging: vchiq: Fixups to Kconfig
Date: Sun, 8 Aug 2021 09:45:28 +0200 [thread overview]
Message-ID: <b2cba890-4838-7b43-c5c4-548f25e14f76@i2se.com> (raw)
In-Reply-To: <cover.1627925241.git.ojaswin98@gmail.com>
Am 02.08.21 um 19:42 schrieb Ojaswin Mujoo:
> Hi everyone,
>
> This patchset performs some minor fixups to the config options defined in
> /staging/vc04_services/Kconfig.
>
> Summary of the patches:
>
> Patch 1: Makes BCM2835_VCHIQ imply VCHIQ_CDEV to make the behavior more
> compatible to how it was before VCHIQ_CDEV was introduced (in
> [1]).
> Patch 2: Add some more details to the configs' help texts
>
>
> Changes since v1 [2]:
>
> * As pre discussion with Greg and Stefan, used "imply" in BCM2835_VCHIQ
> instead of "default y" in VCHIQ_CDEV.
> * Added some more info in help texts of both the config options.
>
> In patch 2, although the resources on VideoCore and vchiq are really
> scattered around the internet, I've tried to keep the help text as
> accurate as possible, as per my knowledge.
> Please do let me know if anything is off in it and I'll fix it.
The whole series is:
Reviewed-by: Stefan Wahren <stefan.wahren@i2se.com>
Thanks
prev parent reply other threads:[~2021-08-08 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 17:42 Ojaswin Mujoo
2021-08-02 17:42 ` [PATCH v2 1/2] staging: vchiq: Set $CONFIG_BCM2835_VCHIQ to imply $CONFIG_VCHIQ_CDEV Ojaswin Mujoo
2021-08-02 17:42 ` [PATCH v2 2/2] staging: vchiq: Add details to Kconfig help texts Ojaswin Mujoo
2021-08-08 7:45 ` Stefan Wahren [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=b2cba890-4838-7b43-c5c4-548f25e14f76@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nsaenz@kernel.org \
--cc=ojaswin98@gmail.com \
--cc=phil@raspberrypi.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
all inboxes | Powered by JetHome®