mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Einon <mark.einon@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	Jiri Pirko <jpirko@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [GIT PATCH] big staging merge for 3.2
Date: Wed, 26 Oct 2011 15:23:01 +0100	[thread overview]
Message-ID: <20111026142301.GA4732@marke.airties> (raw)
In-Reply-To: <CA+55aFxRETDCVs=2pLSbc1qkhUYbfexVO9KG64EP2LKNdXGCeQ@mail.gmail.com>

On Wed, Oct 26, 2011 at 03:59:40PM +0200, Linus Torvalds wrote:
> On Wed, Oct 26, 2011 at 2:07 PM, Greg KH <greg@kroah.com> wrote:
> >
> > Here is the big staging merge for 3.2
> >
> > Note, I ended up merging this with your 3.1 release to resolve a merge
> > issue with one of the comedi drivers to fix a build issue.  If you want
> > me to redo the tree without this merge, I'll be glad to do so and let
> > you do it :)
> 
> I don't hate merges that make sense, and that one looks fine. You
> picked a logical merge point, and you wrote a merge message that
> explains it. No problem.
> 
> > There's a lot of patches in here, and the overall diff is quite
> > impressive:
> >  834 files changed, 103718 insertions(+), 230262 deletions(-)
> 
> Hmm... I only get
> 
>  725 files changed, 103936 insertions(+), 180480 deletions(-)
> 
> Which is still good, but nothing like your numbers. Where did you find
> the extra 50k lines?
> 
> > All patches have been in the -next releases for a while now.
> 
> So I got several conflicts with the networking tree. Most of them were
> trivial (eg driver removal conflicting with somebody trying to fix up
> the now dead driver), but I really hope somebody looks at the
> resulting drivers/staging/et131x/et131x.c file.
> 
> That driver wasn't removed, it was consolidated as one big file, and
> so the fixes to the original files needed to be resolved. I tried to
> do that correctly, but there's the skb_frag_dma_map() change and the
> removal of .ndo_set_multicast_list, and while I think I did it right,
> I really want somebody who knows that code to double check me.
> 
> Appropriate people to do that added to the cc,
> 
>                  Linus

Hi Linus,

The code changes look good, but it also needs the removal of a NETDEV_1000 dependency in the Kconfig file.

I sent a patch for these changes yesterday, you can find it here :
http://www.spinics.net/lists/netdev/msg177938.html

It's practically identical to your fixes, except for the Kconfig change.

Cheers,

Mark

  reply	other threads:[~2011-10-26 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 12:07 Greg KH
2011-10-26 13:59 ` Linus Torvalds
2011-10-26 14:23   ` Mark Einon [this message]
2011-10-26 21:06   ` Greg KH
2011-10-27  1:51     ` Linus Torvalds
2011-10-27 13:47   ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2011-10-25 11:26 Greg KH
2011-10-29 12:24 ` Geert Uytterhoeven

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=20111026142301.GA4732@marke.airties \
    --to=mark.einon@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=devel@linuxdriverproject.org \
    --cc=greg@kroah.com \
    --cc=ian.campbell@citrix.com \
    --cc=jpirko@redhat.com \
    --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

Powered by JetHome