>I cherrypicked five of your patches yesterday as ones which look like
they
>should be in 2.6.14.
>
> fix i386 cmpxchg
> adjust .version updating
> free initrd mem adjustment
> constify font data
> minor fbcon_scroll adjustment
>
>But none of those are NMI-related. Specifically which patch are you
>referring to?
http://marc.theaimsgroup.com/?l=linux-kernel&m=112600003916210&w=2
>...
>> I'd be curious to know how you, considering yourself in my
position,
>> would have approached breaking up and submitting that size a
patch.
>
>a) Patches which affect the main kernel but which aren't really
> debugger-related
So it was right to start with those...
>b) Patches which affect the main kernel and which are
debugger-related
> (adding hooks, generalising interfaces, refactoring functions,
etc).
... and some of those. But you saying this was more or less the right
approach puts things in contradiction with the complaints from others
that consumers of some of the changes weren't immediately visible.
>c) Finally, one monster patch to add the debugger functionality.
Maybe
> split into in vger-sized chunks.
That'll have to follow later.
Thanks, Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |