All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Josh Holland <jrh@joshh.co.uk>
Cc: Greg KH <greg@kroah.com>, Alan Cox <alan@linux.intel.com>,
	Andr? Goddard Rosa <andre.goddard@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Staging: rar: More style changes to rar_driver.c
Date: Tue, 23 Feb 2010 18:05:44 -0800	[thread overview]
Message-ID: <20100224020544.GC13984@suse.de> (raw)
In-Reply-To: <20100220113607.GP24380@polaris.joshh.co.uk>

On Sat, Feb 20, 2010 at 11:36:07AM +0000, Josh Holland wrote:
> On Wed, Feb 17, 2010 at 02:40:46PM -0800, Greg KH wrote:
> > On Fri, Feb 05, 2010 at 09:58:26PM +0000, Josh Holland wrote:
> > > Following advice from Krzysztof Halasa, I made a few changes to the
> > > style bits in rar_driver.c
> > 
> > Can you respin both of these patches in 2 days, against the linux-next
> > tree, as the rar driver author has sent in a bunch of "rename these
> > files" type patches, which caused these to not apply anymore.
> How do I do that? I can't see a linux-next branch in my local repo, and
> I'd rather not download a whole new one...
> 
> $ git remote show origin
> * remote origin
>   URL:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>   HEAD branch: master
>   Remote branch:
>     master tracked
>   Local branch configured for 'git pull':
>     master merges with remote master
>   Local ref configured for 'git push':
>     master pushes to master (up to date)

Google for "linux-next FAQ" for how to set this up properly.

thanks,

greg k-h

      reply	other threads:[~2010-02-24  3:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 21:23 [PATCH] Staging: rar: fixed up rar_driver.{h,c} Josh Holland
2010-02-05  0:32 ` Krzysztof Halasa
2010-02-05 17:19   ` Greg KH
2010-02-05 21:32     ` Krzysztof Halasa
2010-02-05 21:58 ` [PATCH 2/2] Staging: rar: More style changes to rar_driver.c Josh Holland
2010-02-17 22:40   ` Greg KH
2010-02-20 11:36     ` Josh Holland
2010-02-24  2:05       ` 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=20100224020544.GC13984@suse.de \
    --to=gregkh@suse.de \
    --cc=alan@linux.intel.com \
    --cc=andre.goddard@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=jrh@joshh.co.uk \
    --cc=linux-kernel@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.