All of lore.kernel.org
 help / color / mirror / Atom feed
From: "werner" <w.landgraf@ru.ru>
To: anisse@astier.eu, lenb@kernel.org, randy.dunlap@ORACLE.COM,
	linux-kernel@vger.kernel.org
Subject: kernel problem 2.6.33-rc2
Date: Mon, 28 Dec 2009 11:13:18 -0400	[thread overview]
Message-ID: <web-124852048@zbackend1.aha.ru> (raw)


   hello
  
  all the patches don't work. During booting happens the 
same as reported before.
  With 2.6.33-rc1 my server runs nice: 
http://guyane.dyn-o-saur.com/info.php


  
  For transparency, here are: two folders 2.6.33-rc2-git01 
and 02, including the patched subroutines and the patches 
itself what you sent me (however the patchs didnt work 
properly, in dell-wmi and hp-wmi occured errors of 1 hunk 
, so that I ended patching it manually, pls verify the 
subroutines if i patched it right); and the resulting 
kernel packages (including everything: patched source, 
kernel, modules -- please download them only if really 
necessary):
  
    ftp://guyane.dyn-o-saur.com




  I can try still any 2.6.33-rc1-gitX git if you think 
this is senseful. Also, you can send me next patches BUT 
IN THE NORMAL FORMAT OF KERNEL git.bz2 PATCHES (give them 
any -git number) inclusive the Makefile patch, so that I 
don't need patching manually which can result in next 
errors.
  


  W.Landgraf
---
Professional hosting for everyone - http://www.host.ru

             reply	other threads:[~2009-12-28 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 15:13 werner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-25 15:03 kernel problem 2.6.33-rc2 werner
2009-12-26  4:18 ` Len Brown
2009-12-28  4:16   ` Randy Dunlap
2009-12-28  9:34   ` Anisse Astier
2009-12-25  5:37 werner
2009-12-31  9:43 ` Christian Kujau
2010-01-04  2:14   ` Lin Ming
2010-01-12  3:15   ` Len Brown

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=web-124852048@zbackend1.aha.ru \
    --to=w.landgraf@ru.ru \
    --cc=anisse@astier.eu \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@ORACLE.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.