All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Angelo Arrifano <miknix@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [APPLIED] [PATCH 3/3] [ARM] omap850: Use ck_ref clock for omap850.
Date: Tue, 22 Sep 2009 15:36:38 -0700	[thread overview]
Message-ID: <20090922223638.GH4919@atomide.com> (raw)
In-Reply-To: <4AB95230.4090409@gmail.com>

* Angelo Arrifano <miknix@gmail.com> [090922 15:33]:
> Tony Lindgren wrote:
> > This patch has been applied to the linux-omap
> > by youw fwiendly patch wobot.
> > 
> > Branch in linux-omap: omap-fixes
> > 
> > Initial commit ID (Likely to change): 16f038289768a16888e0131471f7c7eb841d36bf
> 
> Just a notice, this patch *as-is* will probably break the tree.
> 
> Current linux-omap still doesn't have a CK_7XX definition, which is
> introduced by "[RFC] OMAP1: Massive clean up of omap730/omap850 code"

OK, let's drop it for now then and then do the massive clean up after
-rc1.

Tony

> 
> Sorry,
> - Angelo
> > 
> > PatchWorks
> > http://patchwork.kernel.org/patch/45810/
> > 
> > Git (Likely to change, and takes a while to get mirrored)
> > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=16f038289768a16888e0131471f7c7eb841d36bf
> > 
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-09-22 22:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05  0:03 [PATCH 3/3] [ARM] omap850: Use ck_ref clock for omap850 Angelo Arrifano
2009-09-22 21:56 ` [APPLIED] " Tony Lindgren
2009-09-22 22:39   ` Angelo Arrifano
2009-09-22 22:36     ` Tony Lindgren [this message]

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=20090922223638.GH4919@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=miknix@gmail.com \
    /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.