You are applying 300 patches all at once? The chance of that working is about zero.
In this specific case what you need to do is read the #3 patch file and see what is wrong and correct it if need be. In the general case we'd apply and the test one change at a time. But you would hope that some other person did this already. Can't you find a later version of the Kernal with all these mods already applied? The kernel is kept in Git and you should be able to find a version with these changes already merged. The days of emailing patch files are long gone. Today we call this a "pull request." Back during the second world war, Werner von Braun was in charge of the German V2 rocket program and it was failing. One V2 after the other blew up during launch or went way off course. Being good engineers his team would do a failure analysis after each attempt then engineers would propose solutions and they would have a meeting to decide the best improvement and then do another launch attempt. This was going slowly. von Braun's boss, Hitler, was wanting to see faster progress. Apparently he did not want to argue with Hitler so von Braun tried a high-risk solution. He asked every engineer on his team "If you could make one change to the rocket what would you change?" and each engineer wrote up one change order. They implemented EVERY change on the next rocket to be launched and it worked. This became the production baseline and later they systematically backed out each change just to see what was going on. So today when someone tries 300 software changes all at once I call it the "Werner von Braun school of software engineering". The method almost never works and I'd suggest it only if your boss is very much like von Braun's boss. On Tue, Jan 14, 2020 at 9:00 AM Gene Heskett <ghesk...@shentel.net> wrote: > Greetings all; > > I have directory with about 300 patches to apply to a kernel tree. > > arranged like this, where pwd is /media/pi/workspace, a 240 G sata SSD on > a usb3 adaptor > > 4.19.y is the kernel tree I want to patch > patches is a directory containing the patches > > cd 4.19.y > patch -p1 ../patches/* reports: > patch: > ../patches/0003-clocksource-drivers-timer-atmel-tcb-add-clockevent-d.patch: > extra operand > > And dies. Thats the 3rd patch file in that tree. And if > I repeat, patch doesn't ask if I want to revert the 1st 2. > > I haven't used patch from the cli in ages. So what am I doing wrong? > > Thanks all. > > Cheers, Gene Heskett > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > If we desire respect for the law, we must first make the law respectable. > - Louis D. Brandeis > Genes Web page <http://geneslinuxbox.net:6309/gene> > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > -- Chris Albertson Redondo Beach, California _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
