linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Josh Boyer" <jwboyer@linux.vnet.ibm.com>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>,
	"Antonino A. Daplas" <adaplas@gmail.com>,
	"Andrei Konovalov" <akonovalov@ru.mvista.com>
Subject: Please pull linux-2.6-virtex.git
Date: Wed, 10 Oct 2007 09:40:36 -0600	[thread overview]
Message-ID: <fa686aa40710100840i33592b91r9066f1c709736fcb@mail.gmail.com> (raw)

Josh, please pull:

git://git.secretlab.ca/git/linux-2.6-virtex.git virtex-for-2.6.24

This tree is based on Paulus' current top-of-tree.

There are some minor changes in here plus the XilinxFB migration to
use of_platform bus.  Normally fb changes go in via the -mm tree; but
I've confirmed with Tony that it's okay to go in via the powerpc tree
(which probably makes sense because it depends on the port of virtex
support to arch/powerpc).  The xilinxfb patches have also been acked
by Andrei, the xilinxfb author.

If I can get an account for patchwork; I can also take responsibility
for updating the state of virtex patches there.

The following changes since commit dcccb37e98e0444b0c6a03b303855771aa463c96:
  Grant Likely (1):
        [POWERPC] Lite5200: Use comma delimiter format for lists in device tree

are available in the git repository at:

  git://git.secretlab.ca/git/linux-2.6-virtex.git virtex-for-2.6.24

Grant Likely (11):
      [POWERPC] XilinxFB: add banner output to probe routine when
DEBUG is defined
      [POWERPC] XilinxFB: Replace calls to printk with dev_dbg, dev_err, etc.
      [POWERPC] XilinxFB: rename failout labels to reflect failure
      [POWERPC] XilinxFB: Split device setup from bus binding
      [POWERPC] XilinxFB: cleanup platform_bus binding to use platform bus API.
      [POWERPC] XilinxFB: add of_platform bus binding
      [POWERPC] XilinxFB: Make missing pdata structure non-fatal
      [POWERPC] XilinxFB: sparse fixes
      [POWERPC] Virtex: Fix URL for Xilinx Virtex support in MAINTAINERS
      [POWERPC] Don't build arch/powerpc/sysdev/dcr.c for ARCH=ppc kernels
      [POWERPC] Uartlite: bootwrapper bug fix, getc loops forever

 MAINTAINERS                  |    2 +-
 arch/powerpc/boot/uartlite.c |    4 +-
 arch/powerpc/sysdev/Makefile |    2 +-
 drivers/video/xilinxfb.c     |  279 ++++++++++++++++++++++++++++++------------
 4 files changed, 203 insertions(+), 84 deletions(-)


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

             reply	other threads:[~2007-10-10 15:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 15:40 Grant Likely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-09  6:07 Please pull linux-2.6-virtex.git Grant Likely
2008-01-09 12:35 ` Josh Boyer
2008-01-09 12:44   ` Peter Korsgaard
2008-01-09 15:03     ` Grant Likely
2008-01-11 13:09       ` Josh Boyer
2008-07-04 17:22 Grant Likely
2008-07-07 12:17 ` Josh Boyer
2008-07-07 14:13   ` John Linn
2008-07-07 14:26     ` John Linn
2008-07-07 14:31       ` Grant Likely
2008-07-09 14:15 ` Josh Boyer
2008-07-09 14:39   ` Grant Likely
2008-07-09 15:57   ` Grant Likely
2008-07-09 16:49     ` Grant Likely

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=fa686aa40710100840i33592b91r9066f1c709736fcb@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=adaplas@gmail.com \
    --cc=akonovalov@ru.mvista.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).