linux-kernel - pull-request: wireless-drivers 2015-02-11

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <87iof8l252.fsf@kamboji.qca.qualcomm.com>
Date:	Wed, 11 Feb 2015 20:43:53 +0200
From:	Kalle Valo <kvalo@....qualcomm.com>
To:	David Miller <davem@...emloft.net>
CC:	<linux-wireless@...r.kernel.org>, <netdev@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: pull-request: wireless-drivers 2015-02-11

Hi Dave,

here's one rtlwifi fix for 3.20. We have had two reports of this issue
already, so it would be good to get this to -rc1 or -rc2.

I rebased wireless-drivers on top of net-next, so this patch applies to
net-next. I hope that's ok.

Kalle

The following changes since commit b0f9ca53cbb103e9240a29a974e0b6085e58f9f7:

  ipv4: Namespecify TCP PMTU mechanism (2015-02-09 18:45:00 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git tags/wireless-drivers-for-davem-2015-02-11

for you to fetch changes up to aeb2d2a4c0ae1739a6e1782bd8c1c96aee8db4e1:

  rtlwifi: Remove logging statement that is no longer needed (2015-02-10 16:09:11 +0200)

----------------------------------------------------------------
rtlwifi:

* remove superfluous warning message which is not needed anymore

----------------------------------------------------------------
Larry Finger (1):
      rtlwifi: Remove logging statement that is no longer needed

 drivers/net/wireless/rtlwifi/pci.c |    5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/