serialice_io_read_filter was being passed the wrong size for words and longs. It was harder to find because serialice_io_read_log was being passed the correct size, and when the filter returns true, the log isn't called.
Signed-off-by: Myles Watson mylesgw@gmail.com
Thanks, Myles
On 07/01/2010 01:20 PM, Myles Watson wrote:
serialice_io_read_filter was being passed the wrong size for words and longs. It was harder to find because serialice_io_read_log was being passed the correct size, and when the filter returns true, the log isn't called.
Signed-off-by: Myles Watsonmylesgw@gmail.com
Sweet, nice catch, does this resolve your issues?
On Thu, Jul 1, 2010 at 1:50 PM, Joseph Smith joe@settoplinux.org wrote:
On 07/01/2010 01:20 PM, Myles Watson wrote:
serialice_io_read_filter was being passed the wrong size for words and longs. It was harder to find because serialice_io_read_log was being passed the correct size, and when the filter returns true, the log isn't called.
Signed-off-by: Myles Watsonmylesgw@gmail.com
Sweet, nice catch, does this resolve your issues?
Not yet, but it's making the debugging easier :)
Thanks, Myles
On Thu, 1 Jul 2010 14:05:18 -0600, Myles Watson mylesgw@gmail.com wrote:
On Thu, Jul 1, 2010 at 1:50 PM, Joseph Smith joe@settoplinux.org wrote:
On 07/01/2010 01:20 PM, Myles Watson wrote:
serialice_io_read_filter was being passed the wrong size for words and longs. It was harder to find because serialice_io_read_log was being passed the correct size, and when the filter returns true, the log isn't called.
Signed-off-by: Myles Watsonmylesgw@gmail.com
Sweet, nice catch, does this resolve your issues?
Not yet, but it's making the debugging easier :)
Good. I think you may have to wait for Stefan for a commit, I think he is the only one with svn write access. Unless Patrick does? Anyways
Acked-by: Joseph Smith joe@settoplinux.org