linux-kernel - Re: [PATCH v2] AHCI: Make distinct names for ports in /proc/interrupts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130514204430.GV6795@mtj.dyndns.org>
Date:	Tue, 14 May 2013 13:44:30 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Alexander Gordeev <agordeev@...hat.com>
Cc:	Jeff Garzik <jgarzik@...ox.com>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org, Jan Beulich <JBeulich@...e.com>
Subject: Re: [PATCH v2] AHCI: Make distinct names for ports in
 /proc/interrupts

On Tue, May 14, 2013 at 09:41:19PM +0200, Alexander Gordeev wrote:
> On Tue, May 14, 2013 at 11:56:42AM -0700, Tejun Heo wrote:
> > On Tue, May 07, 2013 at 10:38:37AM +0200, Alexander Gordeev wrote:
> > > Currently all interrupts assigned to AHCI ports show up in
> > > '/proc/interrupts' as 'ahci'. This fix adds port numbers as
> > > suffixes and hence makes the descriptions distinct.
> > > 
> > > Reported-by: Jan Beulich <JBeulich@...e.com>
> > > Signed-off-by: Alexander Gordeev <agordeev@...hat.com>
> > 
> > Patch doesn't apply.  Can you please refresh it on top of the
> > following git branch?
> 
> Well, this patch is on top of a previously posted another patch
> "[PATCH RFC 1/1] AHCI: Optimize interrupt processing". Jeff said
> he applied the latter, but I did not notice it made to his repo.
> 
> Would you consider to accept "AHCI: Optimize interrupt processing"
> patch first, or still refresh this one?

Can you please repost both on top of for-3.11?

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/