mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: linux-parport@lists.infradead.org
Cc: "Matwey V. Kornilov" <matwey@sai.msu.ru>,
	Greg KH <gregkh@linuxfoundation.org>,
	Heiko Andreas Sommer <hsommer@eso.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-parport] [PATCHv3 2/2] Add force_epp module option for parport_pc.
Date: Thu, 10 Jul 2014 23:48:01 +0200	[thread overview]
Message-ID: <20385712.vl9ZPHu7Ll@indiana> (raw)
In-Reply-To: <CAJs94Eao-ujjZevjptf5hhmkS742HdUVafP4avHR3gx0WzuSTw@mail.gmail.com>

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

Hi,

this thread has been very interesting. I feel that I'm one of the 
"instigators" to solve this f... bug in the kernel. But, it seems that it's 
quiet difficult, more because the kernel developers than the bug itself. 

But well, to be honest, the kernel developers do a great and complex job, so 
probably they have good reasons to react in that way. Think that it's the 
second time that a patch to solve this bug is rejected.

Thanks Matwey for the patch and the afford to solve this bug. I have several 
boxes in the lab where I work (Dell 745) that suffer that false positives.

Also, there's some pci card that also suffer that. I think that we have one. 
But, I'm not sure.

So, I can check whatever could be necessary.

Best regards,

Leopold




-- 
--
Linux User 152692     PGP: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-07-10 21:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07  7:01 Matwey V. Kornilov
2014-07-09 21:29 ` Greg KH
2014-07-10  7:56   ` Matwey V. Kornilov
2014-07-10 14:11     ` Dave Jones
2014-07-10 15:50       ` Matwey V. Kornilov
2014-07-10 17:09     ` Greg KH
2014-07-10 17:32       ` Matwey V. Kornilov
2014-07-10 17:43         ` Greg KH
2014-07-11  6:39           ` Matwey V. Kornilov
2014-07-10 21:48         ` Leopold Palomo-Avellaneda [this message]
2014-07-11 14:12           ` [Linux-parport] " Matwey V. Kornilov
2014-07-10 15:52   ` One Thousand Gnomes
2014-07-10 17:08     ` Greg KH

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=20385712.vl9ZPHu7Ll@indiana \
    --to=leo@alaxarxa.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsommer@eso.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parport@lists.infradead.org \
    --cc=matwey@sai.msu.ru \
    /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®