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: Tue, 26 Jun 2012 19:57:11 +1000 [thread overview]
Message-ID: <4FE98777.4090600@snapgear.com> (raw)
In-Reply-To: <CAMuHMdUmKkiHmEvSo7wgVMdE4=KcGoA=f9eJ_KFkc1OGrqm=3w@mail.gmail.com>
On 06/26/2012 05:47 PM, Geert Uytterhoeven wrote:
> On Tue, Jun 26, 2012 at 7:16 AM, Greg Ungerer<gerg@snapgear.com> wrote:
>> On 06/25/2012 05:59 PM, Geert Uytterhoeven wrote:
>>> On Mon, Jun 25, 2012 at 3:29 AM,<gerg@snapgear.com> wrote:
>>>>
>>>> arch/m68k/include/asm/mcfne.h | 129 +---------
>>>
>>> mcf8390.h?
>>> mcfne.h is queued for removal.
>>
>> I was trying to save it :-)
>> 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.
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
next prev parent reply other threads:[~2012-06-26 9:58 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 [this message]
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
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=4FE98777.4090600@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).