public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Allyn <mark.a.allyn@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] sep: Introduce sep driver
Date: Sun, 21 Nov 2010 09:21:44 -0800	[thread overview]
Message-ID: <20101121172144.GA3703@kroah.com> (raw)
In-Reply-To: <20101121140757.66681d35@lxorguk.ukuu.org.uk>

On Sun, Nov 21, 2010 at 02:07:57PM +0000, Alan Cox wrote:
> On Sat, 20 Nov 2010 08:27:26 -0800
> Greg KH <greg@kroah.com> wrote:
> 
> > On Sat, Nov 20, 2010 at 12:39:11PM +0000, Alan Cox wrote:
> > > 
> > > 
> > > > +/* rar handler */
> > > > +#ifndef CONFIG_MRST_RAR_HANDLER
> > > > +
> > > > +/* This stub header is for non Moorestown driver only */
> > > 
> > > What happened to the patches I sent you a while back that cleaned this
> > > one up ?
> > 
> > Wait, this isn't the cleaned up version?  Ick, should I just drop it and
> > wait for a working one instead?  Or Mark, are you going to fix this one
> > up for real this time?
> 
> I sent Mark a set of follow on patches. Dunno if they got lost in part or
> not. No big deal as they applied on top of his previous set so can just
> be applied as a follow up to the merge.
> 
> So I'd rather you carried on merging them and we'll figure out which of
> the other bits need dropping on top.

Ok, it's in the tree now, but again, it has a ton of build warnings that
should be fixed before I start to get angry emails from Randy about it
:)

thanks,

greg k-h

      reply	other threads:[~2010-11-21 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 23:45 [PATCH 1/1] sep: Introduce sep driver Mark Allyn
2010-11-20  1:20 ` Greg KH
2010-11-20  1:43 ` [PATCH 1/1] Staging: " Greg KH
2010-11-20 12:39 ` [PATCH 1/1] " Alan Cox
2010-11-20 16:27   ` Greg KH
2010-11-21 14:07     ` Alan Cox
2010-11-21 17: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=20101121172144.GA3703@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.a.allyn@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox