mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: krzysztof.h1@poczta.fm
To: "JosephChan@via.com.tw" <JosephChan@via.com.tw>,
	"krzysztof.h1@poczta.fm" <krzysztof.h1@poczta.fm>
Cc: "linux-fbdev-devel@lists.sourceforge.net" 
	<linux-fbdev-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>
Subject: RE: [Linux-fbdev-devel] [PATCH 0/13 v2] viafb: VIA Frame Buffer Device Driver
Date: 11 Aug 2008 11:17:46 +0200	[thread overview]
Message-ID: <20080811091747.045A66D605@f09.poczta.interia.pl> (raw)

> Hi Krzysztof,
> 
> Thanks to remind, but after I checked the patches in linux-fbdev-devel
> mailing list.
> It seems there is no missing lines as you mentioned. 
> 

There are 3 lines missing at the end of each file. I assume they are empty one
so no content is missing but the command:

patch -p1 < viafb3.patch

ends with:
patch: **** malformed patch at line 259: diff -Nurp a/drivers/video/via/accel.h b/drivers/video/via/accel.h

If one adds three lines "+" at the line 259, the patch command ends with:

patching file drivers/video/via/accel.h
patch: **** malformed patch at line 446:

Adding three lines "+" at the mentioned file solves the problem.

Kind regards,
Krzysztof

----------------------------------------------------------------------
Taniej na zagraniczne komorki!
Sprawdz >>> http://link.interia.pl/f1ece


             reply	other threads:[~2008-08-11  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11  9:17 krzysztof.h1 [this message]
2008-08-11 11:57 ` JosephChan
  -- strict thread matches above, loose matches on Subject: below --
2008-08-08 10:09 JosephChan
2008-08-08 16:27 ` [Linux-fbdev-devel] " Krzysztof Helt
2008-08-11  8:03   ` JosephChan
2008-08-09 21:32 ` Bruno Prémont

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=20080811091747.045A66D605@f09.poczta.interia.pl \
    --to=krzysztof.h1@poczta.fm \
    --cc=JosephChan@via.com.tw \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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

all inboxes | Powered by JetHome®