From: linas@austin.ibm.com (Linas Vepstas)
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Greg KH <greg@kroah.com>,
akpm@osdl.org, Alan Cox <alan@redhat.com>,
"Ryan S. Arnold" <rsa@us.ibm.com>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: HVCS char driver janitoring: fix compile warnings
Date: Thu, 16 Nov 2006 18:55:40 -0600 [thread overview]
Message-ID: <20061117005540.GF23600@austin.ibm.com> (raw)
In-Reply-To: <1163716536.16815.5.camel@localhost.localdomain>
On Fri, Nov 17, 2006 at 09:35:36AM +1100, Michael Ellerman wrote:
>
> Thanks, new patches look good.
Any clue who I should send these to? I think akpm took the earlier
one, I'm not clear if that means it will slosh into Linus' tree
eventually.
--linas
next prev parent reply other threads:[~2006-11-17 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 21:26 [PATCH]: HVCS char driver janitoring: fix compile warnings Linas Vepstas
2006-11-16 0:03 ` Michael Ellerman
2006-11-16 20:39 ` Linas Vepstas
2006-11-16 22:35 ` Michael Ellerman
2006-11-17 0:55 ` Linas Vepstas [this message]
2006-11-17 1:11 ` Andrew Morton
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=20061117005540.GF23600@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=rsa@us.ibm.com \
/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