All of lore.kernel.org
 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,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 1/2] m68knommu: reorganize the no-MMU cache flushing to match m68k
Date: Sun, 20 May 2012 21:12:50 +1000	[thread overview]
Message-ID: <4FB8D1B2.8060302@snapgear.com> (raw)
In-Reply-To: <CAMuHMdX48_zgpkRcVwOjLG6ahqZJ8wfLzX0QxhoyWVzh2ZBH+w@mail.gmail.com>

Hi Geert,

On 05/20/2012 07:07 PM, Geert Uytterhoeven wrote:
> On Fri, May 4, 2012 at 8:50 AM,<gerg@snapgear.com>  wrote:
>> In particular by reorganizing the __flush_caceh_all() code and separating
>
> __flush_cache_all()

I'll fix that up.

Thanks for all the other acks too, I'll update the patches.

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-05-20 11:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04  6:50 [PATCH 00/02] m68k: clean up and merge arch dma code gerg
2012-05-04  6:50 ` [PATCH 1/2] m68knommu: reorganize the no-MMU cache flushing to match m68k gerg
2012-05-20  9:07   ` Geert Uytterhoeven
2012-05-20 11:12     ` Greg Ungerer [this message]
2012-05-04  6:50 ` [PATCH 2/2] m68k: merge the MMU and non-MMU versions of the arch dma code gerg
2012-05-20  9:01   ` 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=4FB8D1B2.8060302@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.