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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20090121191320.GA5232@kroah.com>
Date:	Wed, 21 Jan 2009 11:13:20 -0800
From:	Greg KH <greg@...ah.com>
To:	"Altobelli, David" <david.altobelli@...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

On Wed, Jan 21, 2009 at 07:05:03PM +0000, Altobelli, David wrote:
> > -----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.

Ah, yeah, it looks like Andrew took this, which is good, it can go in
through there with no need for me to touch it.

Just cc: him on future patches to make sure he picks them up.

thanks,

greg k-h
--
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/