aic7* claims all checked EISA io ranges
Quoted 4 lines
As far as the 2.4.X series is concerned, pushing has not helped. I've seen spelling fixes and incorrorct changes get accepted from non maintainers "instantly", while the maintainers changes are not
accepted.
Quoted 1 line
Considering how long it took for the last set of driver changes to
make
Quoted 2 lines
it from -ac into kernel.org, I just assumed that this strategy was also failing. Is that really the only way to get updates into
Marcelo's
Quoted 1 line
tree?
I take it 2.5 is up to date, right? Because otherwise we should have seen an update notice go across [email protected].
This problem looks to be present in 2.5, so should I apply the patch?
James
Quoted 2 lines
I take it 2.5 is up to date, right? Because otherwise we should have seen an update notice go across [email protected].
In the past, I have sent mail directly to Linus which has worked for 2.5. Unfortunately, it looks like he has not applied the last bundle I posted to him on 2003/03/25. This is the same bk output as posted on my website.
Quoted 1 line
This problem looks to be present in 2.5, so should I apply the patch?
It would be better to just upgrade the driver with bits I submitted to Linus. I have another update coming to correctly fix the del_timer_sync() issue since the last, unsanctioned, change in this area has a large potential to cause a deadlock.
--
Justin
Quoted 6 lines · Justin T. Gibbs
Quoted 2 lines
I take it 2.5 is up to date, right? Because otherwise we should have seen an update notice go across [email protected].
In the past, I have sent mail directly to Linus which has worked for 2.5. Unfortunately, it looks like he has not applied the last bundle I posted to him on 2003/03/25. This is the same bk output as posted on my website.
Well, the aic7xxx is part of SCSI, and SCSI has an active BK tree for accumulating patches and pushing them to Linus. If you want to circumvent this, then patches will get lost sometimes.
The way to avoid this is to send patches to [email protected].
Quoted 6 lines
Quoted 1 line
This problem looks to be present in 2.5, so should I apply the patch?
It would be better to just upgrade the driver with bits I submitted to Linus. I have another update coming to correctly fix the
del_timer_sync()issue since the last, unsanctioned, change in this area has a large potential to cause a deadlock.
I'll see if I can pull them.
James