On Mon, Nov 02, 2015 at 12:09:31PM -0800, Guenter Roeck wrote:
> On Mon, Nov 02, 2015 at 09:43:56AM -0800, Brian Norris wrote:
> > On Mon, Nov 02, 2015 at 07:41:48AM -0800, Guenter Roeck wrote:
> > > I also see the warning in crisv32 runtime tests. This is because the code
> > > in
> > >
On Mon, Nov 02, 2015 at 09:43:56AM -0800, Brian Norris wrote:
> On Mon, Nov 02, 2015 at 07:41:48AM -0800, Guenter Roeck wrote:
> > Brian,
> >
> > I see the following warnings in recent mips qemu tests on linux-next.
> >
> > WARNING: CPU: 0 PID: 1 at drivers/mtd/mtdcore.c:619
> >
On Mon, Nov 02, 2015 at 07:41:48AM -0800, Guenter Roeck wrote:
> Brian,
>
> I see the following warnings in recent mips qemu tests on linux-next.
>
> WARNING: CPU: 0 PID: 1 at drivers/mtd/mtdcore.c:619
> mtd_device_parse_register+0x160/0x16c()
> MTD already registered
>
> Looking into the
Brian,
I see the following warnings in recent mips qemu tests on linux-next.
WARNING: CPU: 0 PID: 1 at drivers/mtd/mtdcore.c:619
mtd_device_parse_register+0x160/0x16c()
MTD already registered
Looking into the code, this is the result of your patch 'mtd: warn when
registering
the same master
Brian,
I see the following warnings in recent mips qemu tests on linux-next.
WARNING: CPU: 0 PID: 1 at drivers/mtd/mtdcore.c:619
mtd_device_parse_register+0x160/0x16c()
MTD already registered
Looking into the code, this is the result of your patch 'mtd: warn when
registering
the same master
On Mon, Nov 02, 2015 at 07:41:48AM -0800, Guenter Roeck wrote:
> Brian,
>
> I see the following warnings in recent mips qemu tests on linux-next.
>
> WARNING: CPU: 0 PID: 1 at drivers/mtd/mtdcore.c:619
> mtd_device_parse_register+0x160/0x16c()
> MTD already registered
>
> Looking into the
On Mon, Nov 02, 2015 at 09:43:56AM -0800, Brian Norris wrote:
> On Mon, Nov 02, 2015 at 07:41:48AM -0800, Guenter Roeck wrote:
> > Brian,
> >
> > I see the following warnings in recent mips qemu tests on linux-next.
> >
> > WARNING: CPU: 0 PID: 1 at drivers/mtd/mtdcore.c:619
> >
On Mon, Nov 02, 2015 at 12:09:31PM -0800, Guenter Roeck wrote:
> On Mon, Nov 02, 2015 at 09:43:56AM -0800, Brian Norris wrote:
> > On Mon, Nov 02, 2015 at 07:41:48AM -0800, Guenter Roeck wrote:
> > > I also see the warning in crisv32 runtime tests. This is because the code
> > > in
> > >
8 matches
Mail list logo