From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: m8xx_pcmcia.c for v2.6 kernels
Date: Mon, 25 Oct 2004 05:34:31 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0410250532300.27260@localhost.localdomain> (raw)
In-Reply-To: <417C9D25.8060609@intracom.gr>
On Mon, 25 Oct 2004, Pantelis Antoniou wrote:
> Marcelo Tosatti wrote:
>
> > Hi fellows,
> >
> >
> > I'm attaching a port of our internal m8xx_pcmcia.c (based on MontaVista
> > 2.1's 2.4.17 kernel with many fixes) to v2.6.
... huge SNIP here ...
> >
> Marcelo Hi
>
> I'm gonna definately try this and get back to you.
>
> Thanks
>
> Regards
>
> Pantelis
was it absolutely necessary to include 46K worth of patch in your
reply, only to add what you did at the bottom?
rday
next prev parent reply other threads:[~2004-10-25 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 14:27 m8xx_pcmcia.c for v2.6 kernels Marcelo Tosatti
2004-10-25 6:28 ` Pantelis Antoniou
2004-10-25 9:34 ` Robert P. J. Day [this message]
2004-10-25 11:11 ` Pantelis Antoniou
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=Pine.LNX.4.60.0410250532300.27260@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=panto@intracom.gr \
/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).