mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Octavian Purdila <octavian.purdila@intel.com>
To: sameo@linux.intel.com, lee.jones@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	johan@kernel.org, Octavian Purdila <octavian.purdila@intel.com>
Subject: [PATCH v4 0/3] mfd: viperboard: fix cache line sharing and cleanups
Date: Thu, 25 Sep 2014 18:41:34 +0300	[thread overview]
Message-ID: <1411659697-27258-1-git-send-email-octavian.purdila@intel.com> (raw)

Changes since v3:

 * undo a whitespace change

 * one more error path cleanup

 * add commit body to the last patch

Changes since v2:
 
 * switch to using devm_ allocation

 * remove unused platform_device

Changes since v1:

 * split cache sharing fix and cleanups into separate patches


Octavian Purdila (3):
  mfd: viperboard: allocate I/O buffer separately
  mfd: viperboard: switch to devm_ allocation
  mfd: viperboard: remove unused platform_device

 drivers/mfd/viperboard.c       | 18 ++++++++----------
 include/linux/mfd/viperboard.h |  3 +--
 2 files changed, 9 insertions(+), 12 deletions(-)

-- 
1.9.1


             reply	other threads:[~2014-09-25 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 15:41 Octavian Purdila [this message]
2014-09-25 15:41 ` [PATCH v4 1/3] mfd: viperboard: allocate I/O buffer separately Octavian Purdila
2014-09-25 15:52   ` Johan Hovold
2014-09-25 15:41 ` [PATCH v4 2/3] mfd: viperboard: switch to devm_ allocation Octavian Purdila
2014-09-25 15:53   ` Johan Hovold
2014-09-25 15:41 ` [PATCH v4 3/3] mfd: viperboard: remove unused platform_device Octavian Purdila
2014-09-25 15:54   ` Johan Hovold
2014-10-09 20:39 ` [PATCH v4 0/3] mfd: viperboard: fix cache line sharing and cleanups Octavian Purdila

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=1411659697-27258-1-git-send-email-octavian.purdila@intel.com \
    --to=octavian.purdila@intel.com \
    --cc=johan@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sameo@linux.intel.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®