All of lore.kernel.org
 help / color / mirror / Atom feed
From: f6bvp <f6bvp@free.fr>
To: netdev@vger.kernel.org, linux-hams@vger.kernel.org
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Richard Stearn <richard@rns-stearn.demon.co.uk>,
	Bernard Pidoux <bernard.pidoux@free.fr>
Subject: [PATCH 3/6]NET:AX25:ROSE Traps calls to rose_route_frame with a NULL ax25 callback
Date: Sun, 14 Aug 2016 15:41:08 +0200	[thread overview]
Message-ID: <57B074F4.9050307@free.fr> (raw)

Hi Richard,

Thanks for this patch and all others for ROSE code you sent recently.
I already committed a similar one in february 2016.

Subject: [Patch] rose_route_frame() NULL pointer dereference kernel panic
From: f6bvp <f6bvp@xxxxxxx>
Date: Wed, 24 Feb 2016 17:53:11 +0100
Cc: Ralf Baechle <ralf@xxxxxxxxxxxxxx>, "'f6bvp'" <f6bvp@xxxxxxx>, 
davem@xxxxxxxxxxxxx

You may browse linux servers for author f6bvp and see my last findings 
about null ax25.

However, despite all my efforts, I did no convince referees of the 
patch's legitimity and it had not been accepted.
I hope your work for improving rose code will be successful to the 
benefit of all radioamateur packet community!

73 de Bernard, f6bvp


             reply	other threads:[~2016-08-14 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 13:41 f6bvp [this message]
     [not found] ` <57B08A9F.9060208@rns-stearn.demon.co.uk>
2017-02-26 14:09   ` [BUG] unregistered netdevice: wainting for rose0 to become free. Usage count = xx f6bvp
     [not found]     ` <580609a0-7a8d-6e80-98a6-8e91633875ae@free.fr>
2017-03-01 12:48       ` f6bvp
  -- strict thread matches above, loose matches on Subject: below --
2016-07-16  9:43 [PATCH 3/6]NET:AX25:ROSE Traps calls to rose_route_frame with a NULL ax25 callback Richard Stearn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57B074F4.9050307@free.fr \
    --to=f6bvp@free.fr \
    --cc=bernard.pidoux@free.fr \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=richard@rns-stearn.demon.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.