linux-kernel - Re: [PATCH RFC] spi: Dont call prepare/unprepare transfer if not populated

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: <20120515195801.GE23254@lunn.ch>
Date:	Tue, 15 May 2012 21:58:01 +0200
From:	Andrew Lunn <andrew@...n.ch>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Shubhrajyoti D <shubhrajyoti@...com>,
	spi-devel-general@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, andrew@...n.ch
Subject: Re: [PATCH RFC] spi: Dont call prepare/unprepare transfer if not
 populated

On Thu, May 10, 2012 at 09:24:55PM -0600, Grant Likely wrote:
> On Thu, 10 May 2012 16:01:27 +0200, Linus Walleij <linus.walleij@...aro.org> wrote:
> > On Thu, May 10, 2012 at 3:50 PM, Shubhrajyoti D <shubhrajyoti@...com> wrote:
> > 
> > > Currently the prepare/unprepare transfer are called unconditionally.
> > > The assumption is that every driver using the spi core queue infrastructure
> > > has to populate the prepare and unprepare functions. This encourages
> > > drivers to populate empty functions to prevent crashing.
> > > This patch prevents the call to prepare/unprepare if not populated.
> > >
> > > Cc: Linus Walleij <linus.walleij@...aro.org>
> > > Signed-off-by: Shubhrajyoti D <shubhrajyoti@...com>
> > 
> > Great!
> > Acked-by: Linus Walleij <linus.walleij@...aro.org>
> 
> Applied, thanks (after fixing extra whitespace defect).

Hi Grant

Is this going to appear in linux-next soon? Can i depend on having
this patch for 3.5?

     Thanks
	Andrew

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