Message ID | mhng-5ac66c65-9c46-409c-a5fb-a6551bb206c5@palmer-si-x1e (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT,PULL] RISC-V Patches for the 5.2 Merge Window, Part 1 v2 | expand |
On Thu, May 16, 2019 at 5:27 PM Palmer Dabbelt <palmer@sifive.com> wrote: > > > git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git tags/riscv-for-linus-5.2-mw1 Oh no no no. You're creating a binary file from your build or something like that: > modules.builtin.modinfo | Bin 0 -> 46064 bytes which is completely unacceptable. I have no idea what you're doing, but this kind of "random garbage in git commits" is not going to fly. And the fact that you're adding random files really means that you are doing something *horribly* wrong. Linus
On Thu, 16 May 2019 19:17:17 PDT (-0700), Linus Torvalds wrote: > On Thu, May 16, 2019 at 5:27 PM Palmer Dabbelt <palmer@sifive.com> wrote: >> >> >> git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux.git tags/riscv-for-linus-5.2-mw1 > > Oh no no no. > > You're creating a binary file from your build or something like that: > >> modules.builtin.modinfo | Bin 0 -> 46064 bytes > > which is completely unacceptable. > > I have no idea what you're doing, but this kind of "random garbage in > git commits" is not going to fly. And the fact that you're adding > random files really means that you are doing something *horribly* > wrong. Sorry, I have no idea how I missed that. It looks like I managed to screw something up while trying to fix up that patch, but I'm not really sure what I did. I'll try to figure out how to not screw it up next time. Thanks for catching this!