All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>,
	"abbotti@mev.co.uk" <abbotti@mev.co.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: comedi: cleanup alloc_subdevices
Date: Tue, 12 Jun 2012 11:45:48 -0700	[thread overview]
Message-ID: <20120612184548.GA19550@kroah.com> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0020698DBC6D7@AUSP01VMBX24.collaborationhost.net>

On Tue, Jun 12, 2012 at 01:31:38PM -0500, H Hartley Sweeten wrote:
> On Monday, June 11, 2012 6:43 PM, Greg KH wrote:
> > On Mon, Jun 11, 2012 at 07:49:46PM -0500, H Hartley Sweeten wrote:
> >> Also, I have never done local commits to my Linux-next tree so I'm not
> >> sure how to proceed with the incremental patches. If it's ok with you
> >> I'll just wait for each patch to go into staging.
> >
> > Create a brach from the one you are working on:
> > 	git branch -b my_branch
> > make a change and commit it
> > commit another one
> > and so on.
> > then create the patches:
> > 	git format-patch original_branch_name..my_branch
> > and use git send-email to send them off in order.
> >
> > Otherwise we are going to take 7 weeks when I apply one of your patches
> > a week :)
> 
> Greg,
> 
> I did as you described above and have the 7 patches ready but I just
> noticed you have already applied the first one.
> 
> Should I post the entire series and note that the first one is already
> applied?

Yup, that will be fine, I can easily delete that one from my inbox :)

thanks,

greg k-h

  reply	other threads:[~2012-06-12 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 22:08 [PATCH] staging: comedi: cleanup alloc_subdevices H Hartley Sweeten
2012-06-11 23:56 ` Greg KH
2012-06-12  0:07   ` H Hartley Sweeten
2012-06-12  0:44     ` Greg KH
2012-06-12  0:49       ` H Hartley Sweeten
2012-06-12  1:42         ` Greg KH
2012-06-12  2:41           ` Arnaud Lacombe
2012-06-12 18:31           ` H Hartley Sweeten
2012-06-12 18:45             ` Greg KH [this message]
2012-06-12 19:02               ` H Hartley Sweeten

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=20120612184548.GA19550@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abbotti@mev.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=fmhess@users.sourceforge.net \
    --cc=hartleys@visionengravers.com \
    --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.