linux-kernel - RE: [PATCH] hpilo open/close fix

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Jan 2009 19:05:03 +0000
From:	"Altobelli, David" <david.altobelli@...com>
To:	Greg KH <greg@...ah.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"gregkh@...e.de" <gregkh@...e.de>
Subject: RE: [PATCH] hpilo open/close fix

> -----Original Message-----
> From: Greg KH 
> Am I supposed to be shepharding patches to drivers/misc/hpilo into the
> kernel tree?  If so, I've been ignoring it, sorry.  Is there any
> becides this one that you need to go in?
> 

I appreciated your help when I first posted this driver, and you 
are a general driver guy, so I copied you, but I didn't expect you 
to take over shepherding patches into the tree for me.  I don't really 
know how this process works, but I'm happy to copy any person/list that 
will help me move code into the tree.  

I got an email that this patch was in -mm, but I don't know where it 
went from there.

I have a simple add device id patch that I was going to submit after 
figuring out the patch submission process.

--
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/