From: Alexander Gordeev <agordeev@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Jeff Garzik <jgarzik@pobox.com>, Jan Beulich <JBeulich@suse.com>
Subject: [PATCH RESEND 0/1] AHCI: Make distinct names for ports in /proc/interrupts
Date: Tue, 21 May 2013 21:03:05 +0200 [thread overview]
Message-ID: <cover.1369161950.git.agordeev@redhat.com> (raw)
Tejun,
This patch is applied on top of previously (re)sent patch
"AHCI: Optimize interrupt processing". Should the latter
refused, I will post a new version.
Alexander Gordeev (1):
AHCI: Make distinct names for ports in /proc/interrupts
drivers/ata/ahci.c | 5 +++--
drivers/ata/ahci.h | 1 +
drivers/ata/libahci.c | 10 ++++++++++
3 files changed, 14 insertions(+), 2 deletions(-)
--
1.7.7.6
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next reply other threads:[~2013-05-21 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 19:03 Alexander Gordeev [this message]
2013-05-21 19:03 ` [PATCH RESEND 1/1] AHCI: Make distinct names for ports in /proc/interrupts Alexander Gordeev
2013-05-21 23:55 ` [PATCH] AHCI: Make distinct names for ports in /proc/interrupts /proc/interrupts Tejun Heo
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=cover.1369161950.git.agordeev@redhat.com \
--to=agordeev@redhat.com \
--cc=JBeulich@suse.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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