linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: Hemant Kumar <hemantk@codeaurora.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] mhi: unconstify mhi_event_config
Date: Wed, 6 Jan 2021 18:46:16 +0530	[thread overview]
Message-ID: <20210106131616.GG3131@thinkpad> (raw)
In-Reply-To: <CAMZdPi-m9WopviGqH+9XJdg7oi0wA4ASLkyXcqcBqrJdY_Oq8w@mail.gmail.com>

On Wed, Jan 06, 2021 at 09:39:27AM +0100, Loic Poulain wrote:
> Hi Hemant,
> 
> On Wed, 6 Jan 2021 at 03:28, Hemant Kumar <hemantk@codeaurora.org> wrote:
> 
> > Hi Loic
> >
> > On 1/5/21 8:44 AM, Loic Poulain wrote:
> > > Some parameters may have to be determined at runtime.
> > > It is the case for the event ring MSI vector.
> > >
> > > Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
> > > Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > > ---
> > >   v2: no change
> > >
> > >   include/linux/mhi.h | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/include/linux/mhi.h b/include/linux/mhi.h
> > > index 62da830..48b1b2a 100644
> > > --- a/include/linux/mhi.h
> > > +++ b/include/linux/mhi.h
> > > @@ -290,7 +290,7 @@ struct mhi_controller_config {
> > >       u32 num_channels;
> > >       const struct mhi_channel_config *ch_cfg;
> > >       u32 num_events;
> > > -     const struct mhi_event_config *event_cfg;
> > > +     struct mhi_event_config *event_cfg;
> > commented on previous patch set, copying my comment here
> > Do we need to update mhi controller driver like ath11k and generic pci
> > driver to avoid compiler warnings?
> >
> 
> ath11k does declare its mhi_event_config as const so it should not cause
> any issue. mhi_pci_generic event config is modified in 2/2.
> 

Ath11k doesn't declare it as const. It might be an issue before but not now ;)

Thanks,
Mani

> Regards,
> Loic

  parent reply	other threads:[~2021-01-06 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 16:44 [PATCH v2 1/2] mhi: unconstify mhi_event_config Loic Poulain
2021-01-05 16:44 ` [PATCH v2 2/2] mhi: pci_generic: Fix shared MSI vector support Loic Poulain
2021-01-06  2:14   ` Hemant Kumar
2021-01-06 13:20   ` Manivannan Sadhasivam
2021-01-06  2:28 ` [PATCH v2 1/2] mhi: unconstify mhi_event_config Hemant Kumar
     [not found]   ` <CAMZdPi-m9WopviGqH+9XJdg7oi0wA4ASLkyXcqcBqrJdY_Oq8w@mail.gmail.com>
2021-01-06 13:16     ` Manivannan Sadhasivam [this message]
2021-01-06 13:20 ` Manivannan Sadhasivam
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm

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=20210106131616.GG3131@thinkpad \
    --to=manivannan.sadhasivam@linaro.org \
    --cc=hemantk@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    /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).