I used 'git send-email -compose' which opens an editor window to allow me
to document the patch before breaking up the description of the patch in a
separate email. The description attached which came from that email was
not good enough?
Jay
> On 10/13/2010 2:18 PM, [email protected] wrote:
>> From: J Freyensee<[email protected]>
>>
>> ---
>> drivers/char/Kconfig | 36 +++++--
>> drivers/char/Makefile | 1 +
>> drivers/char/n_tracerouter.c | 176 ++++++++++++++++++++++++++--
>> drivers/char/n_tracesink.c | 261
>> ++++++++++++++++++++++++++++++++++++++++++
>> include/linux/pti.h | 5 +-
>> include/linux/tty.h | 2 +-
>> 6 files changed, 458 insertions(+), 23 deletions(-)
>> create mode 100644 drivers/char/n_tracesink.c
>
> I'm sorry, but this patch I can't deal with.
> the previous one was obvious enough for me to invent a description for,
> but this one isn't that trivial...
> please resend with a proper description and Signed-off-by: line
>
>
>
This gives the abiliity to capture modem trace data on multiple MID platforms.
It allows the ability to route modem trace data from one tty to another tty for
later analysis in lab or on a product in the field.
This is the 2nd submission/review for Meego 1.1. This patch has tried to
address all concerns that were raised related to locking, how many tty port
access per SW entity, and debug messages.
This requires the patch that was sent earlier on this list that renames
ptirouter_ldisc to n_tracerouter.
Thanks,
Jay
_______________________________________________
Meego-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
