public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel•crashing.org>
To: "Andre' Draszik" <andid@gmx•net>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH][PPC32] PPC4xx ocp ide rewrite/cleanup
Date: Wed, 16 Feb 2005 18:43:36 -0700	[thread overview]
Message-ID: <20050216184335.A1530@cox.net> (raw)
In-Reply-To: <4213F112.2060606@gmx.net>; from andid@gmx.net on Thu, Feb 17, 2005 at 02:19:14AM +0100

On Thu, Feb 17, 2005 at 02:19:14AM +0100, Andre' Draszik wrote:
> Hi,
> 
> Matt Porter wrote:
> > On Mon, Feb 07, 2005 at 05:24:55AM +0100, Andre' Draszik wrote:
> > 
> >>Hi,
> >>
> >>this is a rewrite of the ibm4xx ocp ide driver. In its current state it
> >>[...]
> > 
> > I tried applying this to current linuxppc-2.5. All hunks are rejected.
> > Can you double check this patch and resend?
> 
> my kernel tree is
> rsync -avz --delete source.mvista.com::linuxppc-2.5 linuxppc-2.5
> and as of 16.02.05 23:44GMT the patch still applies. so did i really
> send a wrong patch or has the rsync mirror just not yet been
> updated? or is it a whitespace issue?
> 
> just checked - it's the last, so here's the patch, rediffed to
> 2.6.11-rc4, as attachment, not inline this time.

Ok, this worked...looks like your mailer mangled whitespace on
the inlined patch. It applied to BK linuxppc-2.5 and I'll take
a look in a bit. Ultimately, we need to get this driver into
linux-2.5.

Thanks,
Matt

  reply	other threads:[~2005-02-17  1:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07  4:24 [PATCH][PPC32] PPC4xx ocp ide rewrite/cleanup Andre' Draszik
2005-02-16 23:14 ` Matt Porter
2005-02-17  1:19   ` Andre' Draszik
2005-02-17  1:43     ` Matt Porter [this message]
2005-02-17 17:35     ` Matt Porter
2005-02-19  9:28       ` Andre' Draszik

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=20050216184335.A1530@cox.net \
    --to=mporter@kernel$(echo .)crashing.org \
    --cc=andid@gmx$(echo .)net \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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