linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards
Date: Wed, 27 Jun 2012 22:48:30 +1000	[thread overview]
Message-ID: <4FEB011E.6090702@snapgear.com> (raw)
In-Reply-To: <CAMuHMdViAKwh+GwS+CWwJ=w5Z=_U-O_isnRDD_RBZ+0hmArX6g@mail.gmail.com>

Hi Geert,

On 06/27/2012 05:34 PM, Geert Uytterhoeven wrote:
> On Wed, Jun 27, 2012 at 4:55 AM, Greg Ungerer<gerg@snapgear.com>  wrote:
>> On 06/26/2012 09:03 PM, Geert Uytterhoeven wrote:
>>> On Tue, Jun 26, 2012 at 12:14 PM, Greg Ungerer<gerg@snapgear.com>    wrote:
>>>> On 06/26/2012 08:03 PM, Geert Uytterhoeven wrote:
>>>>> On Tue, Jun 26, 2012 at 11:57 AM, Greg Ungerer<gerg@snapgear.com>  wrote:
>>>>>> On 06/26/2012 05:47 PM, Geert Uytterhoeven wrote:
>>>>>>>> Do you think I should just silently move the modified mcfne.h
>>>>>>>> to a mcf8390.h?
>>>>>>>
>>>>>>> Sure. Why not?
>>>>>>
>>>>>> We lose any git history linking the original and new file.
>>>>>
>>>>> Your commit renaming-and-modifying it will provide the link?
>>>>
>>>> I would normally do that with a "git mv". But isn't that going to
>>>> clash with your "git rm"? Or am I mis-understanding what you mean?
>>>
>>> It may indeed give a merge conflict.
>>>
>>> If the conflict is too complicated (we'll see in -next), I can remove its
>>> scheduled deletion.
>>
>> My concern here is that I expect that patch will go through DaveM's
>> netdev tree. And he may get a little annoyed when a merge conflict
>
> Point taken.
>
>> arises in Linux next. Given that at this point we have the chance
>> to resolve it.
>
> Removed from scheduled removal.

Fantastic, thanks. I will re-roll the patch moving the mcfne.h to
mcf8390.h, and resend here before I forward on.

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close,                            FAX:         +61 7 3891 3630
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

  reply	other threads:[~2012-06-27 12:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25  1:29 [PATCH 0/2] m68k/net: add support for NS8390 based eth controllers on some ColdFire boards gerg
2012-06-25  1:29 ` [PATCH 1/2] net: " gerg
2012-06-25  7:59   ` Geert Uytterhoeven
2012-06-26  5:16     ` Greg Ungerer
2012-06-26  7:47       ` Geert Uytterhoeven
2012-06-26  9:57         ` Greg Ungerer
2012-06-26 10:03           ` Geert Uytterhoeven
2012-06-26 10:14             ` Greg Ungerer
2012-06-26 11:03               ` Geert Uytterhoeven
2012-06-27  2:55                 ` Greg Ungerer
2012-06-27  7:34                   ` Geert Uytterhoeven
2012-06-27 12:48                     ` Greg Ungerer [this message]
2012-06-25  1:29 ` [PATCH 2/2] m68knommu: platform support for 8390 based ethernet used on some boards gerg

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=4FEB011E.6090702@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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;
as well as URLs for NNTP newsgroup(s).