All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	linux ARM <linux-arm-kernel@lists.infradead.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-pm@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	linux-ide@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
	Richard Purdie <rpurdie@rpsys.net>,
	linux-leds@vger.kernel.org,
	Alessandro Zummo <a.zummo@towertech.it>,
	rtc-linux@googlegroups.com, Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [Patch v3] 0/7] Remove mach-kirkwood
Date: Mon, 1 Sep 2014 16:03:20 +0200	[thread overview]
Message-ID: <20140901140320.GE11312@lunn.ch> (raw)
In-Reply-To: <1997148.5Fa3W8ZmXx@vostro.rjw.lan>

On Mon, Sep 01, 2014 at 03:56:43PM +0200, Rafael J. Wysocki wrote:
> On Saturday, August 30, 2014 06:46:05 PM Andrew Lunn wrote:
> > This is mostly a resend of these patches, removing mach-kirkwood.  Not
> > all maintainers picked up there patches, which has resulted in some
> > dead kernel configuration in v3.17-rcX.
> > 
> > The patch set has been rebased on v3.17-rc2, and it is intended that
> > Jason Cooper will submit them for inclusion in an RC. Subsystem
> > maintainers do not need to do anything.
> > 
> > The last patch "cpufreq: Remove ARCH_KIRKWOOD dependency" is new,
> > since what it is removing was added during v3.16-rcX. It follows the
> > pattern of all the other patches.
> > 
> > Andrew Lunn (7):
> >   cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency
> >   ata: Remove ARCH_KIRKWOOD dependency
> >   thermal: Remove ARCH_KIRKWOOD dependency
> >   leds: Remove ARCH_KIRKWOOD dependency
> >   rtc: Remove ARCH_KIRKWOOD dependency
> >   watchdog: Remove ARCH_KIRKWOOD dependency
> >   cpufreq: Remove ARCH_KIRKWOOD dependency
> 
> I have no problems with these changes, but what exactly am I supposed to do?

Jason will submit the whole series. So an Acked-by: would be nice.

      Andrew

WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v3] 0/7] Remove mach-kirkwood
Date: Mon, 1 Sep 2014 16:03:20 +0200	[thread overview]
Message-ID: <20140901140320.GE11312@lunn.ch> (raw)
In-Reply-To: <1997148.5Fa3W8ZmXx@vostro.rjw.lan>

On Mon, Sep 01, 2014 at 03:56:43PM +0200, Rafael J. Wysocki wrote:
> On Saturday, August 30, 2014 06:46:05 PM Andrew Lunn wrote:
> > This is mostly a resend of these patches, removing mach-kirkwood.  Not
> > all maintainers picked up there patches, which has resulted in some
> > dead kernel configuration in v3.17-rcX.
> > 
> > The patch set has been rebased on v3.17-rc2, and it is intended that
> > Jason Cooper will submit them for inclusion in an RC. Subsystem
> > maintainers do not need to do anything.
> > 
> > The last patch "cpufreq: Remove ARCH_KIRKWOOD dependency" is new,
> > since what it is removing was added during v3.16-rcX. It follows the
> > pattern of all the other patches.
> > 
> > Andrew Lunn (7):
> >   cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency
> >   ata: Remove ARCH_KIRKWOOD dependency
> >   thermal: Remove ARCH_KIRKWOOD dependency
> >   leds: Remove ARCH_KIRKWOOD dependency
> >   rtc: Remove ARCH_KIRKWOOD dependency
> >   watchdog: Remove ARCH_KIRKWOOD dependency
> >   cpufreq: Remove ARCH_KIRKWOOD dependency
> 
> I have no problems with these changes, but what exactly am I supposed to do?

Jason will submit the whole series. So an Acked-by: would be nice.

      Andrew

  reply	other threads:[~2014-09-01 14:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-30 16:46 [Patch v3] 0/7] Remove mach-kirkwood Andrew Lunn
2014-08-30 16:46 ` Andrew Lunn
2014-08-30 16:46 ` [Patch v3] 1/7] cpuidle: kirkwood: Remove ARCH_KIRKWOOD dependency Andrew Lunn
2014-08-30 16:46   ` Andrew Lunn
2014-09-03 13:45   ` Daniel Lezcano
2014-09-03 13:45     ` Daniel Lezcano
2014-08-30 16:46 ` [Patch v3] 2/7] ata: " Andrew Lunn
2014-08-30 16:46   ` Andrew Lunn
2014-08-31 11:02   ` Tejun Heo
2014-08-31 11:02     ` Tejun Heo
2014-08-30 16:46 ` [Patch v3] 3/7] thermal: " Andrew Lunn
2014-08-30 16:46   ` Andrew Lunn
2014-09-02 11:53   ` edubezval
2014-09-02 11:53     ` edubezval at gmail.com
2014-08-30 16:46 ` [Patch v3] 4/7] leds: " Andrew Lunn
2014-08-30 16:46   ` Andrew Lunn
2014-08-30 16:46 ` [Patch v3] 5/7] rtc: " Andrew Lunn
2014-08-30 16:46 ` [Patch v3] 6/7] watchdog: " Andrew Lunn
2014-08-30 16:46   ` Andrew Lunn
2014-08-30 16:46 ` [Patch v3] 7/7] cpufreq: " Andrew Lunn
2014-09-01  4:05   ` Viresh Kumar
2014-09-01 13:56 ` [Patch v3] 0/7] Remove mach-kirkwood Rafael J. Wysocki
2014-09-01 13:56   ` Rafael J. Wysocki
2014-09-01 14:03   ` Andrew Lunn [this message]
2014-09-01 14:03     ` Andrew Lunn
2014-09-01 23:46     ` Rafael J. Wysocki
2014-09-01 23:46       ` Rafael J. Wysocki
2014-09-09 15:10 ` Jason Cooper
2014-09-09 15:10   ` Jason Cooper

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=20140901140320.GE11312@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=a.zummo@towertech.it \
    --cc=daniel.lezcano@linaro.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rpurdie@rpsys.net \
    --cc=rtc-linux@googlegroups.com \
    --cc=rui.zhang@intel.com \
    --cc=tj@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=wim@iguana.be \
    /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.