From: Borislav Petkov <bp@alien8.de>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] ata: uncomment ata_timing for XFER_PIO_SLOW
Date: Fri, 14 Dec 2012 12:51:59 +0100 [thread overview]
Message-ID: <20121214115159.GC7307@liondog.tnic> (raw)
In-Reply-To: <50CB116D.7050701@openvz.org>
On Fri, Dec 14, 2012 at 03:45:49PM +0400, Konstantin Khlebnikov wrote:
> ouch :facepalm: how I missed this... just copy-paste error. sorry again.
No sorries - it can happen to anyone! :-) Keep up the good work.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2012-12-14 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 11:01 [PATCH] ata: uncomment ata_timing for XFER_PIO_SLOW Konstantin Khlebnikov
2012-12-14 11:13 ` Borislav Petkov
2012-12-14 11:45 ` Konstantin Khlebnikov
2012-12-14 11:51 ` Borislav Petkov [this message]
2012-12-14 11:23 ` Alan Cox
2012-12-14 13:47 ` Jeff Garzik
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=20121214115159.GC7307@liondog.tnic \
--to=bp@alien8.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@redhat.com \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
/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