linux-kernel - Re: [PATCH 1/5] drivers/base: Add a DEVICE_BOOL

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

Message-ID: <20121025164319.GA10334@kroah.com>
Date:	Thu, 25 Oct 2012 09:43:19 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Borislav Petkov <bp@...64.org>
Cc:	Tony Luck <tony.luck@...el.com>,
	"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 1/5] drivers/base: Add a DEVICE_BOOL_ATTR macro

On Thu, Oct 25, 2012 at 06:33:48PM +0200, Borislav Petkov wrote:
> On Thu, Oct 25, 2012 at 09:07:41AM -0700, Greg Kroah-Hartman wrote:
> > On Thu, Oct 25, 2012 at 04:17:43PM +0200, Borislav Petkov wrote:
> > > From: Borislav Petkov <bp@...en8.de>
> > > 
> > > ... which, analogous to DEVICE_INT_ATTR provides functionality to
> > > set/clear bools. Its purpose is to be used where values need to be used
> > > as booleans in configuration context.
> > > 
> > > Next patch uses this.
> > > 
> > > Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > > Signed-off-by: Borislav Petkov <bp@...en8.de>
> > 
> > Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > 
> > Do you want me to take this through my tree now?  If not, I have no
> > objection to it being part of this larger series and go to Linus through
> > whatever tree takes it.
> 
> Well, in my case it would go through the RAS tree.

Then I'd recommend it going in that way.

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/