From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Pau Koning <paukoning@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
siwu@hrz.tu-chemnitz.de, Sasha Levin <sasha.levin@oracle.com>,
davem@davemloft.net
Subject: Re: [B.A.T.M.A.N.] [PATCH] net, batman: don't crash on zero length strings in routing_algo
Date: Tue, 25 Dec 2012 03:36:36 +0800 [thread overview]
Message-ID: <201212250336.36874.lindner_marek@yahoo.de> (raw)
In-Reply-To: <CANiGF9_engsHHNUDnJi6+iczCdu7sBV+UuJ+Xv33pGuJxPeuAg@mail.gmail.com>
On Monday, December 24, 2012 23:42:15 Pau Koning wrote:
> On Mon, Dec 24, 2012 at 3:38 PM, Marek Lindner <lindner_marek@yahoo.de>
wrote:
> > On Monday, December 24, 2012 22:18:52 Pau Koning wrote:
> >> On Mon, Nov 19, 2012 at 9:08 PM, Sasha Levin <sasha.levin@oracle.com>
wrote:
> >> > The code that works with routing_algo assumes that the string passed
> >> > is non
> >>
> >> > empty, this assumption is wrong:
> >> Why isn't this patch part of Linux 3.7? It seems to be a bugfix and it
> >> was sent early enough?
> >
> > The patch received a reply mere 2 hours after it was sent. Again, please
> > read all mails before making noise.
>
> Ok, leaving this problem unsolved is the correct way to handle it?
> Nobody is allowed to say anything?
No, of course you are allowed "to say" something. I was simply pointing you to
the explanation why the patch wasn't merged yet.
Cheers,
Marek
next prev parent reply other threads:[~2012-12-24 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 20:08 [PATCH] net, batman: don't crash on zero length strings in routing_algo Sasha Levin
2012-11-19 22:07 ` Antonio Quartulli
2012-12-24 14:18 ` Pau Koning
2012-12-24 14:38 ` [B.A.T.M.A.N.] " Marek Lindner
2012-12-24 15:42 ` Pau Koning
2012-12-24 19:36 ` Marek Lindner [this message]
2012-12-25 8:30 ` Marek Lindner
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=201212250336.36874.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paukoning@gmail.com \
--cc=sasha.levin@oracle.com \
--cc=siwu@hrz.tu-chemnitz.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox