From: Kalle Valo <kvalo@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
Hemant Kumar <quic_hemantk@quicinc.com>,
linux-arm-msm@vger.kernel.org, mhi@lists.linux.dev
Subject: Re: [PATCH v5] bus: mhi: host: make mhi_controller_config::event_cfg const
Date: Tue, 08 Nov 2022 15:33:35 +0200 [thread overview]
Message-ID: <87fsettvtc.fsf@kernel.org> (raw)
In-Reply-To: <20220907080016.GA22505@workstation> (Manivannan Sadhasivam's message of "Wed, 7 Sep 2022 13:30:16 +0530")
Manivannan Sadhasivam <mani@kernel.org> writes:
> On Tue, Aug 30, 2022 at 10:11:47AM -0700, Jeff Johnson wrote:
>> Currently the event_cfg pointer in struct mhi_controller_config is not
>> defined as a const pointer. This prevents clients from registering a
>> read-only configuration unless they use a typecast. Since the
>> event_cfg should not be modified once registered, add the const
>> qualifier to event_cfg. This is aligned with the definition of ch_cfg.
>>
>> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
>
> Applied to mhi-next!
BTW what happened to this patch? I cannot find it anywhere.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-11-08 13:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 21:02 [PATCH v3] bus: mhi: make mhi_controller_config::event_cfg const Jeff Johnson
2022-08-19 21:08 ` Jeffrey Hugo
2022-08-19 21:15 ` Jeff Johnson
2022-08-27 18:43 ` Jeff Johnson
2022-08-29 17:31 ` Manivannan Sadhasivam
2022-08-29 20:51 ` [PATCH v4] bus: mhi: host: " Jeff Johnson
2022-08-30 7:46 ` Manivannan Sadhasivam
2022-08-30 17:12 ` Jeff Johnson
2022-08-30 17:11 ` [PATCH v5] " Jeff Johnson
2022-08-31 8:13 ` Manivannan Sadhasivam
2022-09-07 8:00 ` Manivannan Sadhasivam
2022-11-08 13:33 ` Kalle Valo [this message]
2022-11-08 14:39 ` Manivannan Sadhasivam
2022-11-08 14:58 ` Kalle Valo
2022-11-09 7:45 ` Manivannan Sadhasivam
2022-11-09 15:26 ` Jeff Johnson
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=87fsettvtc.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_hemantk@quicinc.com \
--cc=quic_jjohnson@quicinc.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 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.