<sjg1>
zear: Hi, you don't need to adjust the mac_read_from_eeprom(). Just start your own thing (read_settings() or whatever) - i.e. don't make it any worse. People do appreciate cleanup, but sometimes it can be a big task
neha_ has quit [Quit: Connection closed for inactivity]
<zear>
thanks, that makes sense
<zear>
the problem with cleanups is that they work like a snowball, and I only have limited time :)
torez has joined #u-boot
mps has quit [Ping timeout: 255 seconds]
xroumegue has quit [Ping timeout: 258 seconds]
xroumegue has joined #u-boot
mps has joined #u-boot
<mkorpershoek>
marex: about helping maintaince on usb/gadget part: I'm willing to give a hand. What's the procedure? should I just add my name in the maintainers file and submit a patch? I see that the fastboot stuff is orphaned too. I think I can take that part as well
goliath has quit [Quit: SIGSEGV]
<marex>
mkorpershoek: send a MAINTAINERS patch, CC lukma, thanks a lot
<zear>
speaking of, is usb/next sitting on some different remote than the official repository?
<sjg1>
Forty-Bot: Yes, the pre-run creates it again. Yes use that flag if you use devices...it is mostly useful when you make changes, since then dm needs to recreated things
<Forty-Bot>
ok, thanks; I didn't have it enabled on some tests and they had been spuriously passing since I was using malloc_simple
<sjg1>
Forty-Bot: OK
<Forty-Bot>
maybe we should clear dm_root in dm_test_post_run so things fail earlier
mmu_man has quit [Ping timeout: 255 seconds]
flom84 has joined #u-boot
goliath has joined #u-boot
qqq has joined #u-boot
Stat_headcrabed has joined #u-boot
flom84 has quit [Ping timeout: 255 seconds]
flom84 has joined #u-boot
Stat_headcrabed has quit [Quit: Stat_headcrabed]
* vagrantc
falls behind in tracking u-boot
<vagrantc>
falling behind one release ... what's the worst that could happen :)
qqq has quit [Read error: Connection reset by peer]
qqq has joined #u-boot
persmule has quit [Ping timeout: 252 seconds]
flom84 has quit [Remote host closed the connection]