public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: [GIT PULL] Staging driver fixes for 4.15-rc6
Date: Sun, 31 Dec 2017 12:47:30 +0100	[thread overview]
Message-ID: <20171231114730.GA28429@kroah.com> (raw)

The following changes since commit 1291a0d5049dbc06baaaf66a9ff3f53db493b19b:

  Linux 4.15-rc4 (2017-12-17 18:59:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.15-rc6

for you to fetch changes up to d6b246bb7a29703f53aa4c050b8b3205d749caee:

  staging: android: ion: Fix dma direction for dma_sync_sg_for_cpu/device (2017-12-19 15:53:39 +0100)

----------------------------------------------------------------
Staging fixes for 4.15-rc6

Here are 3 staging driver fixes for 4.15-rc6

The first resolves a bug in the lustre driver that came about due to a
broken cleanup patch, due to crazy list usage in that codebase.  The
remaining two are ion driver fixes, finally getting the CMA interaction
to work properly, resolving two regressions in that area of the code.

All have been in linux-next with no reported issues for a while.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
John Stultz (1):
      staging: ion: Fix ion_cma_heap allocations

NeilBrown (1):
      staging: lustre: lnet: Fix recent breakage from list_for_each conversion

Sushmita Susheelendra (1):
      staging: android: ion: Fix dma direction for dma_sync_sg_for_cpu/device

 drivers/staging/android/ion/Kconfig                |  2 +-
 drivers/staging/android/ion/ion.c                  |  4 ++--
 drivers/staging/android/ion/ion_cma_heap.c         | 15 ++++++++++----
 .../staging/lustre/lnet/klnds/socklnd/socklnd.c    | 23 ++++++++++------------
 4 files changed, 24 insertions(+), 20 deletions(-)

                 reply	other threads:[~2017-12-31 11:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171231114730.GA28429@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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