public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Driver Project <devel@linuxdriverproject.org>
Subject: Re: [GIT PULL] Staging driver patches for 4.6-rc1
Date: Fri, 18 Mar 2016 08:23:48 -0700	[thread overview]
Message-ID: <20160318152348.GA16489@kroah.com> (raw)
In-Reply-To: <CA+55aFwjEefe0s07txUweya+mwx9L4GGY0xGtNtj=xiCA3cHLg@mail.gmail.com>

On Thu, Mar 17, 2016 at 10:19:04PM -0700, Linus Torvalds wrote:
> On Thu, Mar 17, 2016 at 8:25 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > Ok, the diffstat below seems "odd" in that I had done a merge with my
> > char-misc tree to resolve some merge issues a while ago, and that tree
> > is now in your tree, so the diffstat shouldn't be showing it (I updated
> > my master branch), but somehow it is.
> 
> When there isn't a single well-defined common base for the merge
> (which happens when you cross-merge, but also if you have multiple
> different bases internally and then merge inside one branch), the "git
> diff" output will pick one of the (multiple) common bases, and use
> that as the base of the diff.
> 
> That usually works fine, but it can also give wildly wrong diffstat
> results, simply because the only way to get the final real diff would
> be to just do the merge.

Ah, ok, that makes more sense, thanks.

> > Also, there are a number of conflicts here when merging with your tree.
> >         both modified:   drivers/media/dvb-frontends/mn88473.c
> >         deleted by them: drivers/staging/dgap/dgap.c
> >         both modified:   drivers/staging/lustre/lnet/libcfs/linux/linux-crypto.c
> >         both modified:   drivers/staging/media/davinci_vpfe/davinci_vpfe_user.h
> >         both modified:   include/linux/irqdomain.h
> >
> > I can fix these up and resend this with a merged tree pull request if
> > you want me to, it's your call.
> 
> No, all good. I've already merged it, I'm just waiting for the build
> test to finish before pushing out the end result.
> 
> You might want to double-check the end result, but nothing looked
> particularly odd.

All looks good, thanks for doing the merge.

greg k-h

      reply	other threads:[~2016-03-18 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  3:23 [GIT PULL] Staging driver patches for 4.6-rc1 Greg KH
2016-03-18  3:25 ` Greg KH
2016-03-18  5:19   ` Linus Torvalds
2016-03-18 15:23     ` 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=20160318152348.GA16489@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=devel@linuxdriverproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox