From: Mark Salter <msalter@redhat.com>
To: monstr@monstr.eu
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Richard Kuo <rkuo@codeaurora.org>,
linux-hexagon@vger.kernel.org,
James Hogan <james.hogan@imgtec.com>,
linux-metag@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 00/11] Consolidate asm/fixmap.h files
Date: Tue, 12 Nov 2013 10:55:11 -0500 [thread overview]
Message-ID: <1384271711.24631.5.camel@deneb.redhat.com> (raw)
In-Reply-To: <52824BBC.9020401@monstr.eu>
On Tue, 2013-11-12 at 16:39 +0100, Michal Simek wrote:
> On 11/12/2013 02:22 PM, Mark Salter wrote:
> >
> > arch/arm/include/asm/fixmap.h | 25 ++------
> > arch/hexagon/include/asm/fixmap.h | 40 +------------
> > arch/metag/include/asm/fixmap.h | 32 +----------
> > arch/microblaze/include/asm/fixmap.h | 44 +-------------
> > arch/mips/include/asm/fixmap.h | 33 +----------
> > arch/powerpc/include/asm/fixmap.h | 44 +-------------
> > arch/sh/include/asm/fixmap.h | 39 +------------
> > arch/tile/include/asm/fixmap.h | 33 +----------
> > arch/um/include/asm/fixmap.h | 40 +------------
> > arch/x86/include/asm/fixmap.h | 59 +------------------
> > include/asm-generic/fixmap.h | 107 +++++++++++++++++++++++++++++++++++
> > 11 files changed, 125 insertions(+), 371 deletions(-)
> > create mode 100644 include/asm-generic/fixmap.h
>
> Any repo/branch with all these patches will be helpful.
https://github.com/mosalter/linux (fixmap branch)
next prev parent reply other threads:[~2013-11-12 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 13:22 Mark Salter
2013-11-12 13:22 ` [PATCH 01/11] Add generic fixmap.h Mark Salter
2013-11-12 13:46 ` Arnd Bergmann
2013-11-12 13:22 ` [PATCH 02/11] x86: use " Mark Salter
2013-11-12 13:22 ` [PATCH 03/11] arm: " Mark Salter
2013-11-12 14:50 ` Mark Salter
2013-11-12 13:22 ` [PATCH 04/11] hexagon: " Mark Salter
2013-11-18 1:53 ` rkuo
2013-11-12 13:22 ` [PATCH 05/11] metag: " Mark Salter
2013-11-12 14:59 ` James Hogan
2013-11-12 13:22 ` [PATCH 06/11] microblaze: " Mark Salter
2013-11-12 13:22 ` [PATCH 07/11] mips: " Mark Salter
2013-11-21 17:55 ` Ralf Baechle
2013-11-12 13:22 ` [PATCH 08/11] powerpc: " Mark Salter
2013-11-12 13:22 ` [PATCH 09/11] sh: " Mark Salter
2013-11-12 13:22 ` [PATCH 10/11] tile: " Mark Salter
2013-11-13 23:28 ` Chris Metcalf
2013-11-12 13:22 ` [PATCH 11/11] um: " Mark Salter
2013-11-12 13:48 ` Richard Weinberger
2013-11-12 15:39 ` [PATCH 00/11] Consolidate asm/fixmap.h files Michal Simek
2013-11-12 15:55 ` Mark Salter [this message]
2013-11-14 9:39 ` Michal Simek
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=1384271711.24631.5.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=james.hogan@imgtec.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rkuo@codeaurora.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
Powered by JetHome