All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] MMC updates
Date: Wed, 17 Oct 2007 16:48:54 -0400	[thread overview]
Message-ID: <1192654134.15090.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20071017224422.78c082ec@poseidon.drzeus.cx>

On Wed, 2007-10-17 at 22:44 +0200, Pierre Ossman wrote:
> Linus, please pull from
> 
>         git://git.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git for-linus
> 
> The set includes one rare memory leak and some cleanup. It also includes a new frontend for the libertas driver. It is going via my tree because of interdependencies between my tree and the libertas/netdev tree.
> 
>  drivers/mmc/core/mmc.c                  |    3 +-
>  drivers/mmc/host/at91_mci.c             |    4 +-
>  drivers/net/wireless/Kconfig            |    6 +
>  drivers/net/wireless/libertas/Makefile  |    2 +
>  drivers/net/wireless/libertas/defs.h    |    2 +
>  drivers/net/wireless/libertas/if_sdio.c | 1072 +++++++++++++++++++++++++++++++
>  drivers/net/wireless/libertas/if_sdio.h |   45 ++

Libertas bits:

Acked-by: Dan Williams <dcbw@redhat.com>

>  include/linux/mmc/sdio_ids.h            |    6 +
>  8 files changed, 1136 insertions(+), 4 deletions(-)
> 
> Andrew Victor (1):
>       mmc: at91_mci: cleanup: use MCI_ERRORS
> 
> Florin Malita (1):
>       mmc: possible leak in mmc_read_ext_csd
> 
> Pierre Ossman (1):
>       net: libertas sdio driver
> 
> Rgds
> 


  reply	other threads:[~2007-10-17 20:48 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 20:44 [GIT PULL] MMC updates Pierre Ossman
2007-10-17 20:48 ` Dan Williams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-19  7:28 Pierre Ossman
2008-02-09  9:50 Pierre Ossman
2007-12-12 19:12 Pierre Ossman
2007-12-18  7:57 ` Pierre Ossman
2007-11-21 17:56 Pierre Ossman
2007-10-10 19:21 Pierre Ossman
2007-10-12  5:30 ` Linus Torvalds
2007-10-12  5:45   ` Pierre Ossman
2007-10-12 12:18     ` Kay Sievers
2007-10-12 13:53       ` Pierre Ossman
2007-10-12 19:55   ` Pierre Ossman
2007-10-12 20:05     ` Nicolas Pitre
2007-10-12 20:35       ` Pierre Ossman
2007-10-12 21:00       ` Pierre Ossman
2007-10-13  5:29         ` Randy Dunlap
2007-10-13  7:03           ` Pierre Ossman
2007-09-11 15:26 Pierre Ossman
2007-08-23  5:18 Pierre Ossman
2007-08-09 14:34 Pierre Ossman
2007-07-26 13:15 Pierre Ossman
2007-07-21  0:36 Pierre Ossman
2007-07-10 20:43 Pierre Ossman
2007-06-13 17:24 Pierre Ossman
2007-06-08  8:09 Pierre Ossman
2007-05-24  5:46 Pierre Ossman
2007-05-14 16:55 Pierre Ossman
2007-05-08 20:45 Pierre Ossman
2007-05-09  5:55 ` Pierre Ossman
2007-05-09  6:03   ` Nick Piggin
2007-05-09  6:27     ` Pierre Ossman
2007-05-09  6:35       ` Nick Piggin
2007-05-09  7:51         ` Pierre Ossman
2007-05-09  8:05           ` Nick Piggin
2007-05-09  9:11           ` Stefan Richter
2007-05-09 15:44             ` Pierre Ossman
2007-05-01 15:22 Pierre Ossman
2007-05-05  4:24 ` Pierre Ossman
2007-05-05  4:45   ` Linus Torvalds
2007-05-09 18:56 ` Russell King
2007-05-09 19:06   ` Pierre Ossman
2007-05-09 22:12     ` Russell King
2007-05-10  5:44       ` Pierre Ossman
2007-05-10  7:51         ` Russell King
2007-05-10 13:58         ` Pierre Ossman
2007-05-10 14:52           ` Nicolas Pitre
2007-05-12 15:38             ` Nicolas Pitre
2007-05-12 16:12               ` Pierre Ossman
2007-05-12 16:22                 ` Russell King
2007-05-12 17:55                   ` Nicolas Pitre
2007-02-11 15:33 Pierre Ossman
2007-02-04 20:11 Pierre Ossman
2007-01-15  5:46 Pierre Ossman
2007-01-04 12:49 Pierre Ossman
2007-01-10 19:51 ` Pierre Ossman
2006-12-11 11:45 Pierre Ossman

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=1192654134.15090.5.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.