linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Consolidate clks_register() and similar
Date: Tue, 12 Jan 2010 18:57:57 +0000	[thread overview]
Message-ID: <20100112185757.GG5633@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190902089AAB@mi8nycmail19.Mi8.com>

On Tue, Jan 12, 2010 at 12:43:54PM -0500, H Hartley Sweeten wrote:
> You must have merged you patch first.  The removal of line 448:

No - the ep93xx was merged as a whole with the miscellaneous branch,
resulting in no conflicts.  Git is occasionally good with merging.

> -	int i;
> 
> Probably produced a one line fuzz for both patches.  Is everything ok still
> for those two patches?

$ diff -u <(pdb getpatch 5879/1) <(git diff-tree -u 346e34abb2c56695ee4bd6af924141c97a0babfb )
--- /proc/self/fd/63	2010-01-12 18:53:48.958011270 +0000
+++ /proc/self/fd/62	2010-01-12 18:53:48.981135820 +0000
@@ -1,13 +1,9 @@
--------------------------------------------------------------------------------
- arch/arm/mach-ep93xx/clock.c                    |   20 ++++++++++++--------
- arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h |    7 +++++--
- 2 files changed, 17 insertions(+), 10 deletions(-)
--------------------------------------------------------------------------------
+346e34abb2c56695ee4bd6af924141c97a0babfb
 diff --git a/arch/arm/mach-ep93xx/clock.c b/arch/arm/mach-ep93xx/clock.c
-index 1d0f9d8..f77c410 100644
+index 07a58d0..27e3351 100644
 --- a/arch/arm/mach-ep93xx/clock.c
 +++ b/arch/arm/mach-ep93xx/clock.c
-@@ -447,25 +447,29 @@ static int __init ep93xx_clock_init(void)
+@@ -449,25 +449,29 @@ static int __init ep93xx_clock_init(void)
  	u32 value;
  	int i;
  
@@ -44,7 +40,7 @@
 +	/* Initialize the pll2 derived clocks */
  	clk_usb_host.rate = clk_pll2.rate / (((value >> 28) & 0xf) + 1);
  
- 	printk(KERN_INFO "ep93xx: PLL1 running at %ld MHz, PLL2 at %ld MHz\n",
+ 	pr_info("PLL1 running at %ld MHz, PLL2 at %ld MHz\n",
 diff --git a/arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h b/arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h
 index d55194a..cd35912 100644
 --- a/arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h

So the only difference in the patch is the pr_info line.

  reply	other threads:[~2010-01-12 18:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 17:28 [PATCH] Consolidate clks_register() and similar Russell King - ARM Linux
2010-01-10 22:23 ` Jeremy Kerr
2010-01-10 23:12   ` Russell King - ARM Linux
2010-01-11  1:04     ` Ben Dooks
2010-01-11 17:26 ` H Hartley Sweeten
2010-01-11 17:28   ` Russell King - ARM Linux
2010-01-11 22:06 ` Kevin Hilman
2010-01-12 12:17   ` Russell King - ARM Linux
2010-01-12 17:29     ` H Hartley Sweeten
2010-01-12 17:35       ` Russell King - ARM Linux
2010-01-12 17:43         ` H Hartley Sweeten
2010-01-12 18:57           ` Russell King - ARM Linux [this message]
2010-01-12 19:16     ` Kevin Hilman
2010-01-12  0:11 ` Eric Miao

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=20100112185757.GG5633@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).