linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] soc: ti: knav_qmss_queue: export API calls for use by user driver
Date: Thu, 29 Jan 2015 08:33:23 -0800	[thread overview]
Message-ID: <54CA60D3.6090008@oracle.com> (raw)
In-Reply-To: <1422486021-23874-1-git-send-email-m-karicheri2@ti.com>

On 1/28/2015 3:00 PM, Murali Karicheri wrote:
> Currently only few of the API calls are exported. This creates problem
> when the knav* modules are built as modules and another user module
> such as netcp_core try to use these API calls and they are also built
> as module. This patch export these APIs to address the issue.
>
> This is needed to support allmodconfig for ARM
>
> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
> ---
Looks fine. I will pick this up for next merge window.

Regards,
Santosh

      reply	other threads:[~2015-01-29 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 23:00 [PATCH] soc: ti: knav_qmss_queue: export API calls for use by user driver Murali Karicheri
2015-01-29 16:33 ` santosh shilimkar [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=54CA60D3.6090008@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --cc=linux-arm-kernel@lists.infradead.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).