From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm-soc: vt8500: Cleanup patches for 3.7
Date: Mon, 08 Oct 2012 07:14:52 +1300 [thread overview]
Message-ID: <1349633692.9507.7.camel@gitbox> (raw)
In-Reply-To: <201210071123.39535.arnd@arndb.de>
On Sun, 2012-10-07 at 11:23 +0000, Arnd Bergmann wrote:
> On Sunday 07 October 2012, Tony Prisk wrote:
> > Minor cleanup patches for 3.7.
> >
> > Tony Prisk (4):
> > vt8500: Remove unused headers from include/mach/
> > vt8500: Remove arm/boot/compressed/head-vt8500.S
> > vt8500: Fix header in mach-vt8500/timer.c
> > vt8500: Fix build warning when no framebuffer selected
>
> Hi Tony,
>
> The patches all look good, but they are late for 3.7 now. I would
> still take the last one since that fixes a build warning, and the
> separate patch that adds the .dtb files to the Makefile, but leave
> the other ones for 3.8, unless there is a strong reason to
> still include them.
>
> Arnd
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Just to clarify,
Is it only bug-fixes, not cleanup that are being accepted during the
merge-window?
Regards
Tony P
next prev parent reply other threads:[~2012-10-07 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 1:02 [PATCH 0/4] arm-soc: vt8500: Cleanup patches for 3.7 Tony Prisk
2012-10-07 1:02 ` [PATCH 1/4] vt8500: Remove unused headers from include/mach/ Tony Prisk
2012-10-07 1:02 ` [PATCH 2/4] vt8500: Remove arm/boot/compressed/head-vt8500.S Tony Prisk
2012-10-07 1:02 ` [PATCH 3/4] vt8500: Fix header in mach-vt8500/timer.c Tony Prisk
2012-10-07 1:02 ` [PATCH 4/4] vt8500: Fix build warning when no framebuffer selected Tony Prisk
2012-10-07 11:23 ` [PATCH 0/4] arm-soc: vt8500: Cleanup patches for 3.7 Arnd Bergmann
2012-10-07 14:19 ` Olof Johansson
2012-10-07 18:14 ` Tony Prisk [this message]
2012-10-07 18:21 ` Olof Johansson
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=1349633692.9507.7.camel@gitbox \
--to=linux@prisktech.co.nz \
--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 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.