what is the best way to send in a patch for quite a number of
tree-wide (ie., unrelated) typos throughout the source? almost all of
them are innocuous -- either comments or in printed strings, so they
*shouldn't* break anything.
these days, i have a separate "typos" git branch where i just
I'm planning to submit a patch to add LCD support to the current main
Denx (non-AVR32) git.
It consists of the following changes:-
cpu/at32ap/at32ap700x/clk.c |5 +
cpu/at32ap/at32ap700x/portmux.c | 90
+
Mark Jackson wrote:
I'm planning to submit a patch to add LCD support to the current main
Denx (non-AVR32) git.
It consists of the following changes:-
cpu/at32ap/at32ap700x/clk.c |5 +
cpu/at32ap/at32ap700x/portmux.c | 90
On Thu, 2009-06-04 at 08:29 -0400, Jerry Van Baren wrote:
Mark Jackson wrote:
I'm planning to submit a patch to add LCD support to the current main
Denx (non-AVR32) git.
snip
Hi Mark,
Don't agonize over it, just post the patch. The number of electrons you
kill by asking for
4 matches
Mail list logo