On 2014-08-05 23:56, Johan Hovold wrote:
On Tue, Aug 05, 2014 at 02:30:31PM +1000, ress...@ausics.net wrote:
On 2014-08-05 00:10, Johan Hovold wrote:
> I'll queue this up for v3.17-rc.
>
Awesome, any chance of it finding its way into 3.14.x since it's a LT
release?
Yes, it's marked for sta
On Tue, Aug 05, 2014 at 02:30:31PM +1000, ress...@ausics.net wrote:
> On 2014-08-05 00:10, Johan Hovold wrote:
> > I'll queue this up for v3.17-rc.
> >
>
> Awesome, any chance of it finding its way into 3.14.x since it's a LT
> release?
Yes, it's marked for stable and should show up there with
On 2014-08-05 00:10, Johan Hovold wrote:
[ Please, avoid top-posting. ]
Usually I don't but some clients I use just are too much of a PITA to
get it "inline"
On Wed, Jul 30, 2014 at 09:53:39PM +1000, ress...@ausics.net wrote:
Hi Johan,
Thanks you, after running for 12 hours, I am pleased
[ Please, avoid top-posting. ]
On Wed, Jul 30, 2014 at 09:53:39PM +1000, ress...@ausics.net wrote:
> Hi Johan,
>
> Thanks you, after running for 12 hours, I am pleased to say tere are no
> more loggings of this nature using your patch
Great, thanks for testing.
I'll queue this up for v3.17-rc.
Hi Johan,
Thanks you, after running for 12 hours, I am pleased to say tere are no
more loggings of this nature using your patch
Thank you
Ed Butler
On 2014-07-29 22:39, Johan Hovold wrote:
On Wed, Jul 23, 2014 at 10:05:23AM +1000, ress...@ausics.net wrote:
Hi,
I am not familiar with git or
On Wed, Jul 23, 2014 at 10:05:23AM +1000, ress...@ausics.net wrote:
> Hi,
> I am not familiar with git or code writting, I have no idea where to
> start.
> I was reporting the issue so hopefully someone with a clue who had one
> of these dongles might look to see if they experience this and know
On Thu, Jul 24, 2014 at 04:30:21PM +1000, ress...@ausics.net wrote:
> On 2014-07-23 10:14, Greg KH wrote:
> >On Wed, Jul 23, 2014 at 10:05:23AM +1000, ress...@ausics.net wrote:
> >>Hi,
> >>I am not familiar with git or code writting, I have no idea where to
> >>start.
> >
> >You installed your own
On 2014-07-23 10:14, Greg KH wrote:
On Wed, Jul 23, 2014 at 10:05:23AM +1000, ress...@ausics.net wrote:
Hi,
I am not familiar with git or code writting, I have no idea where to
start.
You installed your own kernels from kernel.org, right?
FTP'd the gz file, I extract, copy .config from pr
On Wed, Jul 23, 2014 at 10:05:23AM +1000, ress...@ausics.net wrote:
> Hi,
> I am not familiar with git or code writting, I have no idea where to start.
You installed your own kernels from kernel.org, right?
If so, you have git, and you can read the documentation on 'git bisect'
for how to do this
Hi,
I am not familiar with git or code writting, I have no idea where to
start.
I was reporting the issue so hopefully someone with a clue who had one
of these dongles might look to see if they experience this and know how
to resolve it, if I cant figure it out, might have to go back to 3.12,
On 2014-07-20 11:10, Greg KH wrote:
On Sun, Jul 20, 2014 at 10:43:44AM +0700, Lars Melin wrote:
On 2014-07-20 03:21, Greg KH wrote:
On Sat, Jul 19, 2014 at 03:11:22PM +1000, ress...@ausics.net wrote:
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel log
and dmesg are floode
On Sun, Jul 20, 2014 at 10:43:44AM +0700, Lars Melin wrote:
> On 2014-07-20 03:21, Greg KH wrote:
> >On Sat, Jul 19, 2014 at 03:11:22PM +1000, ress...@ausics.net wrote:
> >>Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel log
> >>and dmesg are flooded with constant messages
> >
On 2014-07-20 03:21, Greg KH wrote:
On Sat, Jul 19, 2014 at 03:11:22PM +1000, ress...@ausics.net wrote:
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel log
and dmesg are flooded with constant messages
option1 ttyUSB0: option_instat_callback: error -2
The device still work
On Sat, Jul 19, 2014 at 03:11:22PM +1000, ress...@ausics.net wrote:
> Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel log
> and dmesg are flooded with constant messages
>
> option1 ttyUSB0: option_instat_callback: error -2
>
> The device still works, it sends and receives SM
Since upgrading from 3.12.24 kernel to 3.14.10, and today, .12 kernel
log and dmesg are flooded with constant messages
option1 ttyUSB0: option_instat_callback: error -2
The device still works, it sends and receives SMS's as well,
I tried setting verbose usb debug to see if it offers any more
e
15 matches
Mail list logo
