linux-kernel - Re: [PATCH 0/2 2.6.30] cxgb3 - notify iWARP of chip resets

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20090126.222119.121000067.davem@davemloft.net>
Date:	Mon, 26 Jan 2009 22:21:19 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	rdreier@...co.com
Cc:	divy@...lsio.com, swise@...ngridcomputing.com,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2 2.6.30] cxgb3 - notify iWARP of chip resets

From: Roland Dreier <rdreier@...co.com>
Date: Mon, 26 Jan 2009 09:57:54 -0800

>  > I'm submitting 2 patches against cxgb3 and iw_cxgb3 respectively.
>  > They are built against net-next-2.6.
>  > The first patch adds a notification mechanism to cxgb3 to alert
>  > the upper layer drivers (iWARP and iSCSI) of a chip reset.
>  > 
>  > The second patch adds the handler for such an event in the iWARP driver.
>  > 
>  > Since the second patch depends on the first one, I submit them together,
>  > even though the second patch should be submitted against Roland's tree.
> 
> simplest thing is for Dave to merge both, and I'm fine with that.

Ok, I'll take care of this.
--
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/