mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J. German Rivera" <German.Rivera@freescale.com>
To: <gregkh@linuxfoundation.org>, <arnd@arndb.de>,
	<devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>
Cc: <stuart.yoder@freescale.com>, <itai.katz@freescale.com>,
	<lijun.pan@freescale.com>, <leoli@freescale.com>,
	<scottwood@freescale.com>, <agraf@suse.de>,
	<bhamciu1@freescale.com>, <R89243@freescale.com>,
	<bhupesh.sharma@freescale.com>, <nir.erez@freescale.com>,
	<richard.schmitt@freescale.com>, <dan.carpenter@oracle.com>
Subject: [PATCH 0/4] staging: fsl-mc: MC command serialization
Date: Wed, 14 Oct 2015 15:11:41 -0500	[thread overview]
Message-ID: <1444853505-1369-1-git-send-email-German.Rivera@freescale.com> (raw)

This patch series depends on the patch series posted
at http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg996780.html

This patch series addresses the following item from the TODO list
for the MC bus driver to exit staging:

* Management Complex (MC) command serialization. Locking mechanisms
  are needed by drivers to serialize commands sent to the MC, including
  from atomic context.

Patch 1: Changed timeout units for MC cmd completion
Patch 2: Refactored mc_send_command()
Patch 3: Added support for atomic portals
Patch 4: Added serialization to mc_send_command()


             reply	other threads:[~2015-10-14 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 20:11 J. German Rivera [this message]
2015-10-14 20:11 ` [PATCH 1/4] staging: fsl-mc: changed timeout units for MC cmd completion J. German Rivera
2015-10-14 20:11 ` [PATCH 2/4] staging: fsl-mc: refactored mc_send_command() J. German Rivera
2015-10-14 20:11 ` [PATCH 3/4] staging: fsl-mc:Added support for atomic portals J. German Rivera
2015-10-14 20:11 ` [PATCH 4/4] staging: fsl-mc: Added serialization to mc_send_command() J. German Rivera
2015-10-17  6:15 ` [PATCH 0/4] staging: fsl-mc: MC command serialization Greg KH
2015-10-17 16:36   ` Jose Rivera
2015-10-17 16:49     ` Greg KH

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=1444853505-1369-1-git-send-email-German.Rivera@freescale.com \
    --to=german.rivera@freescale.com \
    --cc=R89243@freescale.com \
    --cc=agraf@suse.de \
    --cc=arnd@arndb.de \
    --cc=bhamciu1@freescale.com \
    --cc=bhupesh.sharma@freescale.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=itai.katz@freescale.com \
    --cc=leoli@freescale.com \
    --cc=lijun.pan@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir.erez@freescale.com \
    --cc=richard.schmitt@freescale.com \
    --cc=scottwood@freescale.com \
    --cc=stuart.yoder@freescale.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®