All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>, Paul Walmsley <paul@pwsan.com>,
	Tony Lindgren <tony@atomide.com>,
	cpufreq@vger.kernel.org, Dave Jones <davej@redhat.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/6] ARM: OMAP: fix cpufreq build
Date: Mon, 26 Mar 2012 15:07:22 -0700	[thread overview]
Message-ID: <87ehsfrp7p.fsf@ti.com> (raw)
In-Reply-To: <20120326083256.GC22608@n2100.arm.linux.org.uk> (Russell King's message of "Mon, 26 Mar 2012 09:32:56 +0100")

Russell King - ARM Linux <linux@arm.linux.org.uk> writes:

> Kevin,
>
> I only just found this via the arm-soc tree, while trying to merge the
> kautobuildv2 build tree.
>
> You changed my patch and broke it:
>
> config ARM_OMAP2PLUS_CPUFREQ
>         bool "TI OMAP2+"
>         default ARCH_OMAP2PLUS
>         select CPU_FREQ_TABLE
>
> So now, OMAP2 CPUFREQ is selectable on ANYTHING but it will only build
> successfully on OMAP.

Yes, I screwed it up.

I wanted it to be selectable, but majorly screwed it up and it is
certainly not randconfig friendly.

This was also pointed out by Grazvydas soon after merging[1], and I was
expecting a patch from him to remedy that, but I will take care of it
and submit a patch for v3.4-rc right away.
 
> If you're going to change someone elses patch, do them the favour of
> re-posting it back to them for comment *BEFORE* you commit it and send
> it upstream, 

I did.  On Feb 16th, I posted my modified version with you and
linux-arm-kernel Cc'd:

   http://lists.infradead.org/pipermail/linux-arm-kernel/2012-February/085053.html

and then I didn't send the pull request for this for another 3 weeks.

> rather than making it look like they're a total tosser for
> authoring a patch which fucks up other architecture builds.

/me has cache miss on tosser in American jargon cache
/me looks up in urban dictionary.

> Many thanks for that.

Many apologies.

Kevin

[1] http://marc.info/?l=linux-omap&m=133174677506294&w=2


WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] ARM: OMAP: fix cpufreq build
Date: Mon, 26 Mar 2012 15:07:22 -0700	[thread overview]
Message-ID: <87ehsfrp7p.fsf@ti.com> (raw)
In-Reply-To: <20120326083256.GC22608@n2100.arm.linux.org.uk> (Russell King's message of "Mon, 26 Mar 2012 09:32:56 +0100")

Russell King - ARM Linux <linux@arm.linux.org.uk> writes:

> Kevin,
>
> I only just found this via the arm-soc tree, while trying to merge the
> kautobuildv2 build tree.
>
> You changed my patch and broke it:
>
> config ARM_OMAP2PLUS_CPUFREQ
>         bool "TI OMAP2+"
>         default ARCH_OMAP2PLUS
>         select CPU_FREQ_TABLE
>
> So now, OMAP2 CPUFREQ is selectable on ANYTHING but it will only build
> successfully on OMAP.

Yes, I screwed it up.

I wanted it to be selectable, but majorly screwed it up and it is
certainly not randconfig friendly.

This was also pointed out by Grazvydas soon after merging[1], and I was
expecting a patch from him to remedy that, but I will take care of it
and submit a patch for v3.4-rc right away.
 
> If you're going to change someone elses patch, do them the favour of
> re-posting it back to them for comment *BEFORE* you commit it and send
> it upstream, 

I did.  On Feb 16th, I posted my modified version with you and
linux-arm-kernel Cc'd:

   http://lists.infradead.org/pipermail/linux-arm-kernel/2012-February/085053.html

and then I didn't send the pull request for this for another 3 weeks.

> rather than making it look like they're a total tosser for
> authoring a patch which fucks up other architecture builds.

/me has cache miss on tosser in American jargon cache
/me looks up in urban dictionary.

> Many thanks for that.

Many apologies.

Kevin

[1] http://marc.info/?l=linux-omap&m=133174677506294&w=2

  reply	other threads:[~2012-03-26 22:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 10:28 Lost fixes? Russell King - ARM Linux
2012-03-15 10:28 ` Russell King - ARM Linux
2012-03-15 10:29 ` [PATCH 2/6] CPUFREQ: Fix exposure of ARM_EXYNOS4210_CPUFREQ Russell King
2012-03-15 10:30 ` [PATCH 4/6] ARM: OMAP: fix missing __devexit_p() annotations Russell King
2012-03-15 10:30   ` Russell King
2012-03-15 11:06   ` Jean Pihet
2012-03-15 11:06     ` Jean Pihet
2012-03-15 16:59     ` Tony Lindgren
2012-03-15 16:59       ` Tony Lindgren
2012-03-15 10:30 ` [PATCH 5/6] ARM: OMAP2+: I2C: always compile I2C reset code, even if I2C driver is not built Paul Walmsley
2012-03-15 10:30   ` Paul Walmsley
2012-03-15 16:56   ` Tony Lindgren
2012-03-15 16:56     ` Tony Lindgren
2012-03-15 10:31 ` [PATCH 6/6] ARM: OMAP: fix cpufreq build Russell King
2012-03-15 10:31   ` Russell King
2012-03-15 10:31   ` Russell King
2012-03-15 17:10   ` Kevin Hilman
2012-03-15 17:10     ` Kevin Hilman
2012-03-15 18:47     ` Paul Walmsley
2012-03-15 18:47       ` Paul Walmsley
2012-03-26  8:32   ` Russell King - ARM Linux
2012-03-26  8:32     ` Russell King - ARM Linux
2012-03-26 22:07     ` Kevin Hilman [this message]
2012-03-26 22:07       ` Kevin Hilman
2012-03-15 10:44 ` Lost fixes? Samuel Ortiz
2012-03-15 10:44   ` Samuel Ortiz

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=87ehsfrp7p.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=arnd@arndb.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.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.