All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: julia.lawall@lip6.fr, ohad@wizery.com, patrice.chotard@st.com,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] drivers: remoteproc: constify rproc_ops structures
Date: Mon, 2 Jan 2017 01:54:55 -0800	[thread overview]
Message-ID: <20170102095455.GA22853@builder> (raw)
In-Reply-To: <1483267417-7850-1-git-send-email-bhumirks@gmail.com>

On Sun 01 Jan 02:43 PST 2017, Bhumika Goyal wrote:

> Declare rproc_ops structures as const as they are only passed as an
> argument to the function rproc_alloc. This argument is of type const, so
> rproc_ops structures having this property can be declared const too.

Thanks Bhumika, applied.

Regards,
Bjorn

WARNING: multiple messages have this Message-ID (diff)
From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] drivers: remoteproc: constify rproc_ops structures
Date: Mon, 2 Jan 2017 01:54:55 -0800	[thread overview]
Message-ID: <20170102095455.GA22853@builder> (raw)
In-Reply-To: <1483267417-7850-1-git-send-email-bhumirks@gmail.com>

On Sun 01 Jan 02:43 PST 2017, Bhumika Goyal wrote:

> Declare rproc_ops structures as const as they are only passed as an
> argument to the function rproc_alloc. This argument is of type const, so
> rproc_ops structures having this property can be declared const too.

Thanks Bhumika, applied.

Regards,
Bjorn

  reply	other threads:[~2017-01-02  9:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01 10:43 [PATCH v2] drivers: remoteproc: constify rproc_ops structures Bhumika Goyal
2017-01-01 10:43 ` Bhumika Goyal
2017-01-02  9:54 ` Bjorn Andersson [this message]
2017-01-02  9:54   ` Bjorn Andersson

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=20170102095455.GA22853@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=bhumirks@gmail.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=patrice.chotard@st.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.