mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "Greg KH (gregkh@linuxfoundation.org)"
	<gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Subject: Re: 3.0 -> 3.10 regression? poweroff instead of reboot?
Date: Tue, 8 Apr 2014 08:49:53 +0200	[thread overview]
Message-ID: <20140408064953.GH3339@pcnci.linuxbox.cz> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B1AFB7512@HASMSX106.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

Hello Tomas,

> I'm not sure how this is possible that this is failing for you
> 
> if ((0xa301 & 0x600) == 0x200)
> 	goto no_mei; 
> so this is okay, the driver should not bind
> 
> How the patch worked for you before this test?  
> 
> Sorry for asking but can you please double check your compilation setup. 

You're right of course :-(

I tried rebuilding rpm again now, and patch spits following:

Hunk #1 succeeded at 105 (offset -2 lines).
patch unexpectedly ends in middle of line

it's bad rpm build didn't abort at this point, but apparently
this is patch's fault:

[root@dev6 linux-3.10]# cat /tmp/mei/1 | patch -sp1
patch unexpectedly ends in middle of line
[root@dev6 linux-3.10]# echo $?
0

:-(

well, this sucks, I really wouldn't expect that kind of bug in such widely
used program as patch :(

I'll report that.

(btw this error was caused by one whitespace character at last line of patch)

anyways, You can certainly forgot about that, it was my fault :(

sorry about that

nik


>  
> Thanks
> Tomas
> 

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28.rijna 168, 709 00 Ostrava

tel.:   +420 591 166 214
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-04-08  6:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 14:55 Nikola Ciprich
2014-03-29 12:15 ` Nikola Ciprich
2014-03-29 20:37   ` Winkler, Tomas
2014-03-31 12:01     ` Nikola Ciprich
2014-03-31 12:05       ` Winkler, Tomas
2014-03-31 12:11         ` Nikola Ciprich
2014-04-02 13:58         ` Nikola Ciprich
2014-04-02 14:27           ` Winkler, Tomas
2014-04-02 14:36             ` Nikola Ciprich
2014-04-07 13:10               ` Winkler, Tomas
2014-04-07 13:25                 ` Nikola Ciprich
2014-04-07 19:01                   ` Winkler, Tomas
2014-04-08  6:49                     ` Nikola Ciprich [this message]
2014-04-08  6:56                       ` Winkler, Tomas
2014-04-08  7:00                         ` Nikola Ciprich

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=20140408064953.GH3339@pcnci.linuxbox.cz \
    --to=nikola.ciprich@linuxbox.cz \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas.winkler@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome