From: Arnd Bergmann <arnd@arndb.de>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
a.zummo@towertech.it, rtc-linux@googlegroups.com,
linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] m68k RTC fixes
Date: Tue, 03 May 2016 15:49:31 +0200 [thread overview]
Message-ID: <1708606.ou3btFVZ5o@wuerfel> (raw)
In-Reply-To: <20160503134034.GK2335@piout.net>
On Tuesday 03 May 2016 15:40:34 Alexandre Belloni wrote:
> > Queue strategy:
> > 1. These are queued together with Arnd's series,
> > 1. I queue them for v4.7 myself, but then the RTC tree must be mergest
> > after the m68k tree,
> > 2. I queue them for v4.6.
> >
> > As I currently don't have any m68k patches queued for v4.7, perhaps it's
> > easiest if these are included with Arnd's series?
> >
>
> I suggest you take them for 4.7 anyway. I don't think I am confident
> enough to merge Arnd's series for 4.7. Also, I doubt I'll get many acks
> from some architecture maintainers.
>
> So, my plan is to apply it on top of 4.7-rc1 and let it sit in
> linux-next for a while.
>
Good idea. It's getting a bit late for 4.7 now, and there is nothing
urgent in my series.
Arnd
next prev parent reply other threads:[~2016-05-03 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 8:46 [PATCH 0/2] m68k RTC fixes Geert Uytterhoeven
2016-05-02 8:46 ` [PATCH 1/2] m68k/bvme6000: Include generic <linux/rtc.h> Geert Uytterhoeven
2016-05-02 8:46 ` [PATCH 2/2] m68k/mvme16x: " Geert Uytterhoeven
2016-05-03 13:40 ` [PATCH 0/2] m68k RTC fixes Alexandre Belloni
2016-05-03 13:49 ` Arnd Bergmann [this message]
2016-05-03 14:07 ` 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=1708606.ou3btFVZ5o@wuerfel \
--to=arnd@arndb.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox