linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Al Viro" <viro@zeniv.linux.org.uk>,
	"David Howells" <dhowells@redhat.com>,
	"Yoshinori Sato" <ysato@users.sourceforge.jp>,
	"Hans-Christian Egtvedt" <egtvedt@samfundet.no>,
	"Chen Liqin" <liqin.chen@sunplusct.com>,
	"Lennox Wu" <lennox.wu@gmail.com>,
	linux-c6x-dev@linux-c6x.org, Cris <linux-cris-kernel@axis.com>,
	linux@openrisc.net, "Håvard Skinnemoen" <hskinnemoen@gmail.com>,
	"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: Exotic architecture fixes
Date: Tue, 28 May 2013 11:38:02 +0200	[thread overview]
Message-ID: <CAMuHMdXQZcanJLGG8bs7u1CRb2z00Ho-kv4s5044pDDeUvoKeQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdV8gJew_x1+L3O51sB=JU_EvJ-Y05JxKSsXUi+B43HAJA@mail.gmail.com>

On Thu, May 23, 2013 at 10:09 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> I created a branch where I collected several exotic architecture fixes
> (and a few
> other trivial fixes):
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git exotic-arch-fixes
>
> Several of these have been ack'ed (cfr. *-indicators below).
> If you reject any of the commits, please scream.
> If you want to take any of them yourself, please do so.
>
> I intend to merge this into my for-next branch after the release of v3.10-rc4,
> and ask Linus to pull after the release of v3.10-rc5.
> This branch may be rebased.

Rebased against v3.10-rc3.

> Geert Uytterhoeven (32):
>       cris: Switch cris to drivers/Kconfig

JFYI, this has a trivial conflict with "CRIS: drop unused Kconfig symbols"
in -next.

>     * console/font: Refactor font support code selection logic

I inserted a revert of Arnd's 8c090cfbf980581454ae4caae731574fedd7dce8
("staging/solo6x10: depend on CONFIG_FONTS") before this one.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2013-05-28  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 20:09 Exotic architecture fixes Geert Uytterhoeven
2013-05-28  9:38 ` Geert Uytterhoeven [this message]
2013-06-02 19:39   ` Geert Uytterhoeven
2013-06-03  1:28     ` Stephen Rothwell
2013-06-04  7:14       ` Geert Uytterhoeven
2013-05-28 15:53 ` [PATCH] arch/cris: old patch to use hex2bin Andy Shevchenko
2013-05-28 15:53   ` [PATCH] cris: kgdb: use native hex2bin Andy Shevchenko
2013-05-30  7:57     ` Geert Uytterhoeven
2013-05-30  9:09       ` Andy Shevchenko

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=CAMuHMdXQZcanJLGG8bs7u1CRb2z00Ho-kv4s5044pDDeUvoKeQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=egtvedt@samfundet.no \
    --cc=hskinnemoen@gmail.com \
    --cc=lennox.wu@gmail.com \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@openrisc.net \
    --cc=liqin.chen@sunplusct.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=ysato@users.sourceforge.jp \
    /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;
as well as URLs for NNTP newsgroup(s).