From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: linux-parport@lists.infradead.org
Cc: "Matwey V. Kornilov" <matwey@sai.msu.ru>,
Ondrej Zary <linux@rainbow-software.org>,
Greg KH <gregkh@linuxfoundation.org>,
Heiko Andreas Sommer <hsommer@eso.org>,
gnomes@lxorguk.ukuu.org.uk,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-parport] [PATCHv4 2/2] parport: parport_pc: Implement CPU model check to cut off false-positives
Date: Wed, 21 Jan 2015 17:51:09 +0100 [thread overview]
Message-ID: <7486641.U1I25nUFqS@soho> (raw)
In-Reply-To: <CAJs94Ebr_39U4EEQYweuZvXeC0sMdrr7D1EPNae0ujFNTeLq8w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
El Dimecres, 13 d'agost de 2014, a les 12:04:55, Matwey V. Kornilov va
escriure:
> Hi,
>
> What do you think, would it be better just to left the check for all
> x86 32-bit hardware?.
>
Finally,
finally this patch was applied?
Best regards,
Leopold
--
--
Linux User 152692 GPG: 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 --]
next prev parent reply other threads:[~2015-01-21 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 7:12 [PATCHv4 0/2] parport: parport_pc: Fix false-positives at checking for Intel bug matwey
2014-07-18 7:12 ` [PATCHv4 1/2] parport: parport_pc: Introduce intel_bug_present function matwey
2014-07-18 7:12 ` [PATCHv4 2/2] parport: parport_pc: Implement CPU model check to cut off false-positives matwey
2014-07-18 7:31 ` Ondrej Zary
2014-08-13 8:04 ` Matwey V. Kornilov
2015-01-21 16:51 ` Leopold Palomo-Avellaneda [this message]
2015-01-21 17:09 ` [Linux-parport] " Matwey V. Kornilov
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=7486641.U1I25nUFqS@soho \
--to=leo@alaxarxa.net \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hsommer@eso.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=linux@rainbow-software.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 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.