Hi James,
Perhaps Michael and Sam would be interested in sharing the role, for atari
and sun3 NCR5380 drivers (?)
If you insist ...
(kidding - I"m OK with it if James thinks it's worth it)
As long as you understand how it works and how to fix it, the more the
merrier. It gives me more people
Hi James,
Perhaps Michael and Sam would be interested in sharing the role, for atari
and sun3 NCR5380 drivers (?)
If you insist ...
(kidding - Im OK with it if James thinks it's worth it)
As long as you understand how it works and how to fix it, the more the
merrier. It gives me more people
On Tue, 2014-04-29 at 15:15 +1200, Michael Schmitz wrote:
> Finn,
>
> On Tue, Apr 29, 2014 at 2:22 PM, Finn Thain
> wrote:
> >
> > On Sat, 26 Apr 2014, James Bottomley wrote:
> >
> >> OK, so this is a pretty big change to an unmaintained driver. I'll take
> >> it if you're willing to maintain
On Tue, 2014-04-29 at 15:15 +1200, Michael Schmitz wrote:
Finn,
On Tue, Apr 29, 2014 at 2:22 PM, Finn Thain fth...@telegraphics.com.au
wrote:
On Sat, 26 Apr 2014, James Bottomley wrote:
OK, so this is a pretty big change to an unmaintained driver. I'll take
it if you're willing to
Finn,
On Tue, Apr 29, 2014 at 2:22 PM, Finn Thain wrote:
>
> On Sat, 26 Apr 2014, James Bottomley wrote:
>
>> OK, so this is a pretty big change to an unmaintained driver. I'll take
>> it if you're willing to maintain the driver afterwards ... in which case
>> I need another patch to add you to
On Sat, 26 Apr 2014, James Bottomley wrote:
> OK, so this is a pretty big change to an unmaintained driver. I'll take
> it if you're willing to maintain the driver afterwards ... in which case
> I need another patch to add you to the MAINTAINERS file.
Sure, I'm happy to support these patches
On Sat, 26 Apr 2014, James Bottomley wrote:
OK, so this is a pretty big change to an unmaintained driver. I'll take
it if you're willing to maintain the driver afterwards ... in which case
I need another patch to add you to the MAINTAINERS file.
Sure, I'm happy to support these patches
Finn,
On Tue, Apr 29, 2014 at 2:22 PM, Finn Thain fth...@telegraphics.com.au wrote:
On Sat, 26 Apr 2014, James Bottomley wrote:
OK, so this is a pretty big change to an unmaintained driver. I'll take
it if you're willing to maintain the driver afterwards ... in which case
I need another
On Wed, 2014-03-19 at 23:35 +1100, Finn Thain wrote:
> This patch series addresses several issues with NCR5380 drivers:
>
> 1. The complex network of #include directives.
>
> 2. Three inconsistent implementations of the core driver all attempting
>to share the same macro definitions in
On Wed, 2014-03-19 at 23:35 +1100, Finn Thain wrote:
This patch series addresses several issues with NCR5380 drivers:
1. The complex network of #include directives.
2. Three inconsistent implementations of the core driver all attempting
to share the same macro definitions in NCR5380.h.
Acked-by: Sam Creasey
On Wed, Mar 19, 2014 at 11:35:16PM +1100, Finn Thain wrote:
>
> This patch series addresses several issues with NCR5380 drivers:
>
> 1. The complex network of #include directives.
>
> 2. Three inconsistent implementations of the core driver all attempting
>to share
Acked-by: Sam Creasey sa...@sammy.net
On Wed, Mar 19, 2014 at 11:35:16PM +1100, Finn Thain wrote:
This patch series addresses several issues with NCR5380 drivers:
1. The complex network of #include directives.
2. Three inconsistent implementations of the core driver all attempting
to
This patch series addresses several issues with NCR5380 drivers:
1. The complex network of #include directives.
2. Three inconsistent implementations of the core driver all attempting
to share the same macro definitions in NCR5380.h.
3. Broken debugging code.
In the past these issues have
This patch series addresses several issues with NCR5380 drivers:
1. The complex network of #include directives.
2. Three inconsistent implementations of the core driver all attempting
to share the same macro definitions in NCR5380.h.
3. Broken debugging code.
In the past these issues have
14 matches
Mail list logo