public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	b.a.t.m.a.n@lists.open-mesh.org, akpm@linux-foundation.org,
	Antonio Quartulli <a@unstable.cc>,
	Simon Wunderlich <sw@simonwunderlich.de>
Subject: Re: [B.A.T.M.A.N.] [PATCH 3.16 076/294] batman-adv: fix TT sync flag inconsistencies
Date: Tue, 7 Nov 2017 02:16:51 +0100	[thread overview]
Message-ID: <20171107011651.GB1873@otheros> (raw)
In-Reply-To: <lsq.1510009382.466414456@decadent.org.uk>

Hi Ben!

On Mon, Nov 06, 2017 at 11:03:02PM +0000, Ben Hutchings wrote:
> 3.16.50-rc1 review patch.  If anyone has any objections, please let me know.
> 
> ------------------
> 
> From: Linus Lüssing <linus.luessing@c0d3.blue>
> 
> commit 54e22f265e872ae140755b3318521d400a094605 upstream.
[...]
> [bwh: Backported to 3.16:
>  - Drop changes to batadv_tt_global_dump_subentry()

May I ask, were there specific concerns for stable 3.16 kernel
releases with this change?

It's not bothering me, but I'm currently wondering whether
this could cause some confusion to users.

Regards, Linus

       reply	other threads:[~2017-11-07  1:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lsq.1510009377.526284287@decadent.org.uk>
     [not found] ` <lsq.1510009382.466414456@decadent.org.uk>
2017-11-07  1:16   ` Linus Lüssing [this message]
2017-11-07 13:42     ` [B.A.T.M.A.N.] [PATCH 3.16 076/294] batman-adv: fix TT sync flag inconsistencies Ben Hutchings
2017-11-12 19:55       ` Linus Lüssing

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=20171107011651.GB1873@otheros \
    --to=linus.luessing@c0d3.blue \
    --cc=a@unstable.cc \
    --cc=akpm@linux-foundation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sw@simonwunderlich.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