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: Alan Cox <alan@linux.intel.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fix a silly typo
Date: Mon, 30 Nov 2009 08:59:18 -0800	[thread overview]
Message-ID: <20091130165918.GA29035@kroah.com> (raw)
In-Reply-To: <20091130163937.092f10e9@lxorguk.ukuu.org.uk>

On Mon, Nov 30, 2009 at 04:39:37PM +0000, Alan Cox wrote:
> On Mon, 30 Nov 2009 08:14:05 -0800
> Greg KH <greg@kroah.com> wrote:
> 
> > On Mon, Nov 30, 2009 at 01:24:49PM +0000, Alan Cox wrote:
> > > (Resend #3)
> > > 
> > > Signed-off-by: Alan Cox <alan@linux.intel.com>
> > > ---
> > > 
> > >  drivers/staging/rtl8187se/r8180_core.c  |    2 +-
> > >  drivers/staging/rtl8192su/r8192U_core.c |    2 +-
> > >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > This is due to changes in Rusty's tree, not mine.  You aren't the only
> > one constantly sending this patch, Randy is as well.
> 
> Well given Rusty has vanished can you apply it to staging and rusty can
> fix his tree up when he returns, assuming patch doesn't fix it for him.

The patch does not apply to my tree at all, the problem is caused by
stuff done only in Rusty's tree.  He has changed the code here to be
broken, not me, so there's really nothing I can do about it.

Stephen could apply it to linux-next though.

thanks,

greg k-h

  reply	other threads:[~2009-11-30 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 13:24 [PATCH] staging: fix a silly typo Alan Cox
2009-11-30 16:09 ` Randy Dunlap
2009-11-30 16:14 ` Greg KH
2009-11-30 16:39   ` Alan Cox
2009-11-30 16:59     ` Greg KH [this message]
2009-12-01  2:07       ` Rusty Russell
2009-12-01  1:58   ` Rusty Russell

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=20091130165918.GA29035@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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