public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eric Dumazet <eric.dumazet@gmail.com>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: linux-next: manual merge of the staging-next tree with the net tree
Date: Fri, 23 Jul 2010 09:09:31 +0200	[thread overview]
Message-ID: <201007230909.32763.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <20100723150323.daa04d5f.sfr@canb.auug.org.au>

[-- Attachment #1: Type: Text/Plain, Size: 1264 bytes --]

Stephen Rothwell wrote:
> Hi Greg,
> 
> Today's linux-next merge of the staging-next tree got a conflict in
> drivers/staging/batman-adv/hard-interface.c between commit
> 28172739f0a276eb8d6ca917b3974c2edb036da3 ("net: fix 64 bit counters on 32
> bit arches") from the net tree and commit
> a1a38cad4c71bc08403b204fbe0ba98b4447f8bf ("Staging: batman-adv: Don't
> increment stats of foreign device") from the staging-next tree.
> 
> The latter just removes the code fixed by the former, so I did that.

That is absolutely correct. The netdev guys noticed that the commits around 
"net: fix 64 bit counters on 32 bit arches" made those lines a real bug 
(casting stuff around, writing on memory it should only read, probably writing 
on unrelated memory). We reviewed those lines again and noticed that they make 
no sense at all and removed them to fix that bug and another minor bug.

I am sorry that this created a merge conflict for you, but only those commits 
by the netdev guys made us aware that there is something going wrong in the 
batman-adv receive code.

Thanks a lot for your linux-next repository and your work on it. It is a big 
help to see what is going on elsewhere and how it may affect our code.

Best regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-07-23  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23  5:03 linux-next: manual merge of the staging-next tree with the net tree Stephen Rothwell
2010-07-23  7:09 ` Sven Eckelmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-05-06  4:05 Stephen Rothwell
2010-05-06  4:20 ` Greg KH
2010-05-06  4:21   ` Stephen Rothwell
2010-05-06  6:21     ` Greg KH
2010-04-27  4:26 Stephen Rothwell
2010-04-27 15:13 ` Greg KH

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=201007230909.32763.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.de \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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