On Mon, Nov 13, 2017 at 11:51:59AM -0600, Alan Tull wrote:
> On Tue, Oct 31, 2017 at 9:22 PM, Alan Tull wrote:
>
> Any further comments on v5? I'm getting ready to send v6. If I do it
> today, most of these patches will have no changes (again), the only
> changes will be in
On Mon, Nov 13, 2017 at 11:51:59AM -0600, Alan Tull wrote:
> On Tue, Oct 31, 2017 at 9:22 PM, Alan Tull wrote:
>
> Any further comments on v5? I'm getting ready to send v6. If I do it
> today, most of these patches will have no changes (again), the only
> changes will be in the patches that
On Tue, Oct 31, 2017 at 9:22 PM, Alan Tull wrote:
Any further comments on v5? I'm getting ready to send v6. If I do it
today, most of these patches will have no changes (again), the only
changes will be in the patches that move drvdata out of the common
code.
I've gone to a
On Tue, Oct 31, 2017 at 9:22 PM, Alan Tull wrote:
Any further comments on v5? I'm getting ready to send v6. If I do it
today, most of these patches will have no changes (again), the only
changes will be in the patches that move drvdata out of the common
code.
I've gone to a lot of trouble to
On Tue, Oct 31, 2017 at 8:34 PM, Moritz Fischer wrote:
> On Tue, Oct 31, 2017 at 04:45:54PM -0500, Alan Tull wrote:
>> On Tue, Oct 31, 2017 at 3:59 PM, Moritz Fischer wrote:
>> > On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote:
>> >> Changes to the
On Tue, Oct 31, 2017 at 8:34 PM, Moritz Fischer wrote:
> On Tue, Oct 31, 2017 at 04:45:54PM -0500, Alan Tull wrote:
>> On Tue, Oct 31, 2017 at 3:59 PM, Moritz Fischer wrote:
>> > On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote:
>> >> Changes to the fpga manager code to not use drvdata
On Tue, Oct 31, 2017 at 04:45:54PM -0500, Alan Tull wrote:
> On Tue, Oct 31, 2017 at 3:59 PM, Moritz Fischer wrote:
> > On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote:
> >> Changes to the fpga manager code to not use drvdata in common
> >> code.
> >>
> >> Change
On Tue, Oct 31, 2017 at 04:45:54PM -0500, Alan Tull wrote:
> On Tue, Oct 31, 2017 at 3:59 PM, Moritz Fischer wrote:
> > On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote:
> >> Changes to the fpga manager code to not use drvdata in common
> >> code.
> >>
> >> Change fpga_mgr_register to
On Tue, Oct 31, 2017 at 3:59 PM, Moritz Fischer wrote:
> On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote:
>> Changes to the fpga manager code to not use drvdata in common
>> code.
>>
>> Change fpga_mgr_register to not set or use drvdata.
>>
>> Change the
On Tue, Oct 31, 2017 at 3:59 PM, Moritz Fischer wrote:
> On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote:
>> Changes to the fpga manager code to not use drvdata in common
>> code.
>>
>> Change fpga_mgr_register to not set or use drvdata.
>>
>> Change the register/unregister function
On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote:
> Changes to the fpga manager code to not use drvdata in common
> code.
>
> Change fpga_mgr_register to not set or use drvdata.
>
> Change the register/unregister function parameters to take the mgr
> struct:
> * int
On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote:
> Changes to the fpga manager code to not use drvdata in common
> code.
>
> Change fpga_mgr_register to not set or use drvdata.
>
> Change the register/unregister function parameters to take the mgr
> struct:
> * int
Changes to the fpga manager code to not use drvdata in common
code.
Change fpga_mgr_register to not set or use drvdata.
Change the register/unregister function parameters to take the mgr
struct:
* int fpga_mgr_register(struct device *dev,
struct fpga_manager *mgr);
* void
Changes to the fpga manager code to not use drvdata in common
code.
Change fpga_mgr_register to not set or use drvdata.
Change the register/unregister function parameters to take the mgr
struct:
* int fpga_mgr_register(struct device *dev,
struct fpga_manager *mgr);
* void
14 matches
Mail list logo