linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: linuxppc-dev@ozlabs.org
Cc: Paul Mackerras <paulus@samba.org>
Subject: Re: Commits added to powerpc.git master and powerpc-next branches
Date: Tue, 1 Jul 2008 10:49:29 +0200	[thread overview]
Message-ID: <200807011049.32699.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <18537.30774.608486.268257@cargo.ozlabs.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Hi Paul,

On Tuesday 01 July 2008, Paul Mackerras wrote:
> The following commits have been added to the master and powerpc-next
> branches of the powerpc.git repository.  This includes patches pulled
> from Kumar's and Josh's trees.

Any change of getting the following patches into 2.6.27 ? They have either been acked and not picked, or just ignored so far :-/

[PATCHv2] fs_enet: restore promiscuous and multicast settings in restart()
	http://patchwork.ozlabs.org/linuxppc/patch?person=968&id=19228
[PATCH 2/2] fs_enet: MDIO on GPIO support
	http://patchwork.ozlabs.org/linuxppc/patch?person=968&id=18693
[PATCHv3 1/2] [POWERPC] CPM2: Implement GPIO LIB API on CPM2 Freescale SoC.
	http://patchwork.ozlabs.org/linuxppc/patch?person=968&id=19045
[PATCH] powerpc: Modem control lines support for the cpm_uart driver
	http://patchwork.ozlabs.org/linuxppc/patch?person=968&id=17928
[PATCH] cpm_uart: Support uart_wait_until_sent()
	http://patchwork.ozlabs.org/linuxppc/patch?person=968&id=19233

Best regards,

-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-07-01  8:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  0:20 Commits added to powerpc.git master and powerpc-next branches Paul Mackerras
2008-07-01  1:27 ` Paul Mackerras
2008-07-01  1:45   ` Benjamin Herrenschmidt
2008-07-01  2:30     ` Josh Boyer
2008-07-01  2:44       ` Benjamin Herrenschmidt
2008-07-01  4:05         ` Kumar Gala
2008-07-01  2:01   ` Paul Mackerras
2008-07-01  4:01 ` [PATCH 0/2] powerpc: Update VSX support Michael Neuling
2008-07-01  4:01   ` [PATCH 1/2] powerpc: Fix compile error for CONFIG_VSX Michael Neuling
2008-07-01  4:51     ` Michael Neuling
2008-07-01  4:01   ` [PATCH 2/2] powerpc: Update for VSX core file and ptrace Michael Neuling
2008-07-01  7:00 ` [PATCH] powerpc: fix compile warning in init_thread Michael Neuling
2008-07-01  9:07   ` Benjamin Herrenschmidt
2008-07-01 11:02     ` Michael Neuling
2008-07-01  8:49 ` Laurent Pinchart [this message]
2008-07-01 15:54   ` Commits added to powerpc.git master and powerpc-next branches Jochen Friedrich
2008-07-02  7:42     ` Kumar Gala
2008-07-02 12:35       ` Jochen Friedrich
2008-07-02 15:10         ` Kumar Gala
2008-07-02  7:41   ` Kumar Gala
2008-07-02  8:41     ` Laurent Pinchart
2008-07-02  1:56 ` [PATCH] powerpc: cleanup copy_to/from_user for vsx and fpr Michael Neuling
2008-07-02  4:06   ` Michael Neuling

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=200807011049.32699.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).