All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Elise Lennion <elise.lennion@gmail.com>
Cc: hvaibhav.linux@gmail.com, johan@kernel.org, elder@kernel.org,
	outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 1/7] staging: greybus: Format block comments.
Date: Wed, 12 Oct 2016 16:40:15 +0200	[thread overview]
Message-ID: <20161012144015.GA28533@kroah.com> (raw)
In-Reply-To: <20161012135508.GC5158@lennorien.com>

On Wed, Oct 12, 2016 at 10:55:08AM -0300, Elise Lennion wrote:
> On Wed, Oct 12, 2016 at 03:24:01PM +0200, Greg KH wrote:
> > 
> > Does not apply to my tree :(
> > 
> > Can you refresh this whole series and resend it?  Keep the acks that
> > were sent for some of the patches, and fix up the subject: lines.
> > 
> 
> Ok, I'll create new patches containing the changes without ack.

No, keep the acks, why delete them?

> This one that doesn't apply, should I just drop it? Your tree is local
> so I can't see what is different, to adjust the changes, until you push
> the changes to staging-testing, right?

My tree is pushed to staging-testing, so you should see this now.  Is it
not synced up somehow?

thanks,

greg k-h


  parent reply	other threads:[~2016-10-12 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11  3:11 [PATCH 1/7] staging: greybus: Format block comments Elise Lennion
2016-10-12 13:24 ` Greg KH
2016-10-12 13:55   ` Elise Lennion
2016-10-12 14:03     ` [Outreachy kernel] " Julia Lawall
2016-10-12 14:40     ` Greg KH [this message]
2016-10-12 15:52       ` Elise Lennion
2016-10-13  5:19         ` [Outreachy kernel] " Julia Lawall
2016-10-13 21:22           ` Elise Lennion
2016-10-12 17:21       ` Elise Lennion
2016-10-12 17:33   ` Elise Lennion

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=20161012144015.GA28533@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=elder@kernel.org \
    --cc=elise.lennion@gmail.com \
    --cc=hvaibhav.linux@gmail.com \
    --cc=johan@kernel.org \
    --cc=outreachy-kernel@googlegroups.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.