driverdev-devel.linuxdriverproject.org archive mirror
 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: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Staging driver fixes for 5.5-rc3
Date: Fri, 20 Dec 2019 08:08:08 +0100	[thread overview]
Message-ID: <20191220070808.GA2190290@kroah.com> (raw)

The following changes since commit d1eef1c619749b2a57e514a3fa67d9a516ffa919:

  Linux 5.5-rc2 (2019-12-15 15:16:08 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-5.5-rc3

for you to fetch changes up to c05c403b1d123031f86e65e867be2c2e9ee1e7e3:

  staging: wfx: fix wrong error message (2019-12-18 15:51:06 +0100)

----------------------------------------------------------------
Staging driver fixes for 5.5-rc3

Here are some small staging driver fixes for a number of reported
issues.

The majority here are some fixes for the wfx driver, but also in here is
a comedi driver fix found during some code review, and an axis-fifo
build dependancy issue to resolve some reported testing problems.

All of these have been in linux-next with no reported issues.

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

----------------------------------------------------------------
Brendan Higgins (1):
      staging: axis-fifo: add unspecified HAS_IOMEM dependency

Ian Abbott (1):
      staging: comedi: gsc_hpdi: check dma_alloc_coherent() return value

Jérôme Pouiller (10):
      staging: wfx: fix the cache of rate policies on interface reset
      staging: wfx: fix case of lack of tx_retry_policies
      staging: wfx: fix counter overflow
      staging: wfx: use boolean appropriately
      staging: wfx: firmware does not support more than 32 total retries
      staging: wfx: fix rate control handling
      staging: wfx: ensure that retry policy always fallbacks to MCS0 / 1Mbps
      staging: wfx: detect race condition in WEP authentication
      staging: wfx: fix hif_set_mfp() with big endian hosts
      staging: wfx: fix wrong error message

 drivers/staging/axis-fifo/Kconfig         |  2 +-
 drivers/staging/comedi/drivers/gsc_hpdi.c | 10 +++++++++
 drivers/staging/wfx/data_tx.c             | 35 ++++++++++++++++++++++---------
 drivers/staging/wfx/data_tx.h             |  5 +++--
 drivers/staging/wfx/hif_tx_mib.h          |  1 -
 drivers/staging/wfx/main.c                |  2 +-
 drivers/staging/wfx/queue.c               |  1 +
 drivers/staging/wfx/sta.c                 |  6 +++++-
 8 files changed, 46 insertions(+), 16 deletions(-)
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

             reply	other threads:[~2019-12-20  7:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  7:08 Greg KH [this message]
2019-12-20 18:15 ` [GIT PULL] Staging driver fixes for 5.5-rc3 pr-tracker-bot

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=20191220070808.GA2190290@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;
as well as URLs for NNTP newsgroup(s).