All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vipin Mehta <vmehta@atheros.com>, linux-next@vger.kernel.org
Subject: Re: [Vipin.Mehta@Atheros.com: [PATCH] staging: ath6kl: Fixing the driver to use modified mmc_host structure
Date: Wed, 29 Sep 2010 19:21:40 -0700	[thread overview]
Message-ID: <20100930022140.GA4035@kroah.com> (raw)
In-Reply-To: <20100930105748.5b049c44.sfr@canb.auug.org.au>

On Thu, Sep 30, 2010 at 10:57:48AM +1000, Stephen Rothwell wrote:
> Hi Vipin,
> 
> On Wed, 29 Sep 2010 17:34:19 -0700 Vipin Mehta <vmehta@atheros.com> wrote:
> >
> >     Can you pls help me apply the following patch to the linux-next 
> > tree. The patch fixes a compilation problem with ath6kl due to a
> > change in the mmc_host structure. The driver compiles fine in the
> > staging-next-2.6 tree which is where the changes for this driver 
> > actually go. However, the mmc stack in the linux-next tree and 
> > staging-next-2.6 is out of sync and so this patch is only applicable
> > to linux-next.
> 
> I will carry it as a merge fixup patch for the staging-next tree.
> Someone just needs to make sure that this patch gets applied (or sent to
> Linus) at the right time.

I'll keep in my "todo" file to handle it when the merge happens.

thanks,

greg k-h

      reply	other threads:[~2010-09-30  2:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30  0:34 [Vipin.Mehta@Atheros.com: [PATCH] staging: ath6kl: Fixing the driver to use modified mmc_host structure Vipin Mehta
2010-09-30  0:57 ` Stephen Rothwell
2010-09-30  2:21   ` Greg KH [this message]

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=20100930022140.GA4035@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vmehta@atheros.com \
    /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.