Re: [PATCH] libbb: rename two fields in ioloop_state, no logic changes
Victor Erminpour via busybox <[email protected]> Tue, 21 Apr 2026 12:21:51 -0700
| Newsgroups | gmane.linux.busybox |
|---|---|
| Message-ID | <CAHwirtGUN4ZVoJp5NAguHxbcSncLyH_Yequ-fPb1jULyAYTBEQ@mail.gmail.com> |
HI all, Please forgive the additional incorrect patches sent, the patch I meant to send was the first one: [PATCH] tc: make CBQ support optional and isolate legacy code I was having issues with building for RISC-V with a newer kernel (>=6.3). Please include it if you find it useful. I'm a big fan of the busybox project, thanks for all the great work! Regards, --Victor On Tue, Apr 21, 2026 at 12:07 PM Guillermo Rodriguez Garcia <[email protected]> wrote: > > > El El mar, 21 abr 2026 a las 20:35, Roberto A. Foglietta <[email protected]> escribió: >> >> On Tue, 21 Apr 2026 at 19:24, Guillermo Rodriguez Garcia >> <[email protected]> wrote: >> > >> > El El mar, 21 abr 2026 a las 16:54, Roberto A. Foglietta <[email protected]> escribió: >> >> >> >> On Tue, 21 Apr 2026 at 12:23, Guillermo Rodriguez Garcia via busybox >> >> <[email protected]> wrote: >> >> > >> >> > Hi Victor, >> >> > >> >> > This patch is already included in git. I assume you did not mean to send it ? >> >> > >> >> >> >> My interpretation of sending that patch is: the git.busybox.net >> >> changed during a period of downtime, therefore some people did not >> >> accept that >> > >> > >> > It is simpler than that. He’s sending a patch that is not his own, and is taken from git HEAD. Probably a mistake with git format-patch or similar. >> > >> >> Irrelevant, because he sent a patch of his own as well > > > Of course but obviously I am not talking about that one. I simply warned him that he had sent an additional patch that was already in git. > > Guillermo Rodriguez Garcia > [email protected] > _______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox