rmilecki has quit [Quit: Konversation terminated!]
rmilecki has joined #openwrt-devel
rmilecki has quit []
rmilecki has joined #openwrt-devel
rmilecki has quit []
rmilecki has joined #openwrt-devel
tSYS has quit [Quit: *squeak*]
tSYS has joined #openwrt-devel
Mangix has quit [Ping timeout: 480 seconds]
rua has quit [Quit: Leaving.]
Mangix has joined #openwrt-devel
rua has joined #openwrt-devel
ChriChri has quit [Ping timeout: 480 seconds]
rua has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
ChriChri has joined #openwrt-devel
rua has joined #openwrt-devel
goliath has joined #openwrt-devel
rua has quit [Quit: Leaving.]
robimarko has joined #openwrt-devel
mcbridematt has quit [Ping timeout: 480 seconds]
robimarko has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
<robimarko>
Is anyone seeing a weird config behaviour?
<robimarko>
I set my config via menuconfig, then save it, but after the first make run it will rescan the targets again and then throw that config is out of sync?
<Habbie>
i'm pretty sure i read something like that in here earlier this week
<Ansuel>
open issue and please tag me or i will forget
<xback>
will do
<Ansuel>
robimarko thing should be improved... there are still some really big corner case but IMHO they are not worth to handle... In such condition the user will have much worse problem (corner case is a .config and you just change the target with a dirty config... it will work but you will have dependency of the previous target... having the update the config 2 times won't be a problem in such broken condition)
xback has quit [Quit: Konversation terminated!]
xback has joined #openwrt-devel
xback has quit [Remote host closed the connection]
Tapper has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
<dwfreed>
Ansuel: I did some looking into xback's report already, because Tapper reported the same in #openwrt earlier; tim->virtual_map is a flex array, but is specified as size 1, so the fortify check complains
<dwfreed>
Ansuel: this is an upstream kernel bug
<robimarko>
Ansuel: That should be fine enough
<Ansuel>
dwfreed yep and i think it should also be already fixed
<Ansuel>
or eventually it's just a patch to backport?