All of lore.kernel.org
 help / color / mirror / Atom feed
From: sukeshs@broadcom.com
To: gregkh@suse.de
Cc: devel@linuxdriverproject.org, linux-wireless@vger.kernel.org
Subject: [PATCH 0/2] *** SUBJECT HERE ***
Date: Tue, 3 May 2011 00:00:55 -0700	[thread overview]
Message-ID: <1304406057-8722-1-git-send-email-sukeshs@broadcom.com> (raw)

From: Sukesh Srikakula <sukeshs@xl-sj1-20.sj.broadcom.com>

*** BLURB HERE ***

Sukesh Srikakula (2):
  brcm80211: FIX for TKIP GTK bug
  brcm80211: Fix for suspend/resume bug

 drivers/staging/brcm80211/brcmfmac/bcmsdh_sdmmc.c |    4 ----
 drivers/staging/brcm80211/brcmfmac/dhd.h          |    3 +++
 drivers/staging/brcm80211/brcmfmac/dhd_linux.c    |    6 ++++--
 drivers/staging/brcm80211/brcmfmac/wl_cfg80211.c  |   12 ++++++++++++
 4 files changed, 19 insertions(+), 6 deletions(-)

-- 
1.7.3.2



             reply	other threads:[~2011-05-03  7:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03  7:00 sukeshs [this message]
2011-05-03  7:00 ` [PATCH 1/2] brcm80211: FIX for TKIP GTK bug sukeshs
2011-05-03  7:00 ` [PATCH 2/2] brcm80211: Fix for suspend/resume bug sukeshs
2011-05-03  9:10   ` Arend van Spriel
2011-05-03 12:15   ` Greg KH
2011-05-03 12:33     ` Arend van Spriel
2011-05-03 13:00       ` Greg KH
2011-05-03 13:09         ` Arend van Spriel
2011-05-03 13:11           ` Greg KH
2011-05-03 13:17             ` Arend van Spriel
2011-05-03 13:41               ` Arend van Spriel
2011-05-03 19:46                 ` Greg KH
2011-05-03 12:14 ` [PATCH 0/2] *** SUBJECT HERE *** Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2024-03-30  6:41 lixiaoyong
2023-03-11 12:54 Sergey Lisov
2023-03-11 12:54 Sergey Lisov
2023-03-11 12:54 Sergey Lisov
2022-09-02  1:58 sieu.mun.tang
2022-08-31 11:20 Jit Loon Lim
2021-05-07  4:36 Saurav Girepunje
2021-05-07  6:00 ` Greg KH
2021-05-07  6:18   ` SAURAV GIREPUNJE
2021-04-16  8:07 Tao Zhang
2021-04-16  8:11 ` Greg Kroah-Hartman
2021-04-16  8:11   ` Greg Kroah-Hartman
2019-03-11 15:04 Colin Watson
2019-03-13  9:56 ` Daniel Kiper
2019-03-13 10:12   ` Colin Watson
2019-03-13 10:22     ` Daniel Kiper
2016-03-13 19:50 Andrew Pinski
2016-03-13 19:50 ` Andrew Pinski
2014-06-18 15:34 Claire Murphy
2013-11-20 22:02 Chris Zankel
2013-07-10 13:14 Damien Millescamps
2013-06-19  0:05 Anders Hammarquist
2013-06-19 22:53 ` Greg KH
2013-06-21 23:08   ` Anders Hammarquist
2013-06-21 23:56     ` Greg KH
2013-06-22 18:54       ` Anders Hammarquist
2013-06-25 23:39         ` Greg KH
2013-06-26  8:29           ` Anders Hammarquist
2013-06-26 10:39             ` Johan Hovold
2013-06-27 21:50               ` Anders Hammarquist
2013-06-28 10:23                 ` Johan Hovold
2013-07-01 23:22                   ` Anders Hammarquist
2013-07-02  9:46                     ` Johan Hovold
2010-11-29 17:56 Arnaldo Carvalho de Melo
2010-01-06  4:30 [RFC/PATCH 0/2] Updates to improve device tree support Bill Gatliff
2010-01-06  4:30 ` [PATCH 0/2] *** SUBJECT HERE *** Bill Gatliff
2010-01-06  4:32   ` Bill Gatliff
2009-06-10 11:51 Izik Eidus
2009-06-08  4:31 Junio C Hamano
2008-08-29  8:16 [PATCH 0/6] 'git svn info' fixes Eric Wong
2008-08-29 13:42 ` [PATCH 0/2] *** SUBJECT HERE *** Thomas Rast

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=1304406057-8722-1-git-send-email-sukeshs@broadcom.com \
    --to=sukeshs@broadcom.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@suse.de \
    --cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.