linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: adaplas@pol.net, adaplas@hotpop.com,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 8/10] fbdev: Allow core fb to be built as a module
Date: Mon, 7 Mar 2005 16:39:12 -0800	[thread overview]
Message-ID: <20050307163912.14f9f0d4.akpm@osdl.org> (raw)
In-Reply-To: <9e4733910503071605486c9c93@mail.gmail.com>

Jon Smirl <jonsmirl@gmail.com> wrote:
>
> Here's the same patch as an attachment. It is against a clean linus bk tree.

Tony has already sent a monster fbdev Kconfig cleanup patch, so your latest
patch does:

patching file drivers/video/Kconfig
Hunk #2 FAILED at 112.
Hunk #3 FAILED at 120.
Hunk #4 FAILED at 144.
Hunk #5 FAILED at 201.
Hunk #6 succeeded at 292 (offset 80 lines).
Hunk #7 FAILED at 300.
Hunk #8 FAILED at 393.
Hunk #9 FAILED at 410.
Hunk #10 succeeded at 421 (offset 57 lines).
Hunk #11 FAILED at 432.
Hunk #12 FAILED at 447.
Hunk #13 FAILED at 493.
Hunk #14 FAILED at 598.
Hunk #15 succeeded at 1121 (offset 167 lines).
Hunk #16 succeeded at 1075 (offset 76 lines).
Hunk #17 FAILED at 1093.
Hunk #18 FAILED at 1115.
Hunk #19 FAILED at 1123.
14 out of 19 hunks FAILED -- saving rejects to file drivers/video/Kconfig.rej
patching file drivers/video/Makefile
Hunk #1 FAILED at 8.
1 out of 1 hunk FAILED -- saving rejects to file drivers/video/Makefile.rej
patching file drivers/video/console/Makefile
patching file drivers/video/fbmem.c
Hunk #1 succeeded at 1205 (offset 1 line).


I assume that Tony must have fixed up your original or something.

Sorry, but at this stage of the kernel cycle when I'm 800-900 patches away
from Linus, things are a bit difficult.  A fixup patch against
http://www.zip.com.au/~akpm/linux/patches/stuff/x.bz2 would really be
ideal, please.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-08  0:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06  0:16 [PATCH 8/10] fbdev: Allow core fb to be built as a module Antonino A. Daplas
2005-03-07  8:36 ` Andrew Morton
2005-03-07  9:39   ` Geert Uytterhoeven
2005-03-07 10:28 ` Andrew Morton
2005-03-07 18:20   ` Jon Smirl
2005-03-07 19:11   ` Jon Smirl
2005-03-07 23:43     ` Andrew Morton
2005-03-08  0:05       ` Jon Smirl
2005-03-08  0:39         ` Andrew Morton [this message]
2005-03-08  0:35       ` Jon Smirl
2005-03-08  0:48         ` Andrew Morton
2005-03-08  1:18           ` Randy.Dunlap
2005-03-08  1:47         ` Andrew Morton
2005-03-08  4:50           ` Jon Smirl
2005-03-08  4:58             ` Andrew Morton
2005-03-09  5:48               ` Antonino A. Daplas
2005-03-09  6:50                 ` 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=20050307163912.14f9f0d4.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=jonsmirl@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).