From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Daniele Pala <dandario@libero.it>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.5.69 drivers/macintosh/adbhid.c && QUESTIONS
Date: 11 May 2003 22:46:04 +0200 [thread overview]
Message-ID: <1052685963.12188.120.camel@gaston> (raw)
In-Reply-To: <20030507153134.GA344@libero.it>
On Wed, 2003-05-07 at 17:31, Daniele Pala wrote:
> This fixes a supid syntax error in adbhid.c
> The question is: is there a PPC mantainer who i must send patches for PPC? or i just drop them here in the list?
> There are other few errors in PPC related files that sometimes prevents the kernel from compiling...supid things, but
> annoying...so who gets the PPC stuff?
There is a PowerMac maintainer, me ;) Though I've been a bit busy with
other things than 2.5 PowerMac drivers lately, still send me the patches.
You will also have more luck using the bk://ppc.bkbits.net/linuxppc-2.5
tree until all of our stuff is properly merged upstream
Ben.
prev parent reply other threads:[~2003-05-11 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 15:31 PATCH 2.5.69 drivers/macintosh/adbhid.c && QUESTIONS Daniele Pala
2003-05-11 20:46 ` Benjamin Herrenschmidt [this message]
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=1052685963.12188.120.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=dandario@libero.it \
--cc=linux-kernel@vger.kernel.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