All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: devel@driverdev.osuosl.org, andrew@lunn.ch, f.fainelli@gmail.com,
	vivien.didelot@savoirfairelinux.com, nikolay@cumulusnetworks.com,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	idosch@mellanox.com, jiri@mellanox.com,
	razvan.stefanescu@nxp.com, gregkh@linuxfoundation.org,
	Petr Machata <petrm@mellanox.com>,
	davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next v3 0/7] net: bridge: Notify about bridge VLANs
Date: Tue, 29 May 2018 13:58:53 +0300	[thread overview]
Message-ID: <20180529105853.GA13795@splinter.mtl.com> (raw)
In-Reply-To: <20180529104609.jqbql6ts2rbb7k3l@mwanda>

On Tue, May 29, 2018 at 01:46:09PM +0300, Dan Carpenter wrote:
> It occured to me that I should read the cover letter and here are the
> answers I was looking for.  But the cover letter isn't saved after the
> commits are merged.

DaveM adds the cover letter to the merge commit.

WARNING: multiple messages have this Message-ID (diff)
From: Ido Schimmel <idosch@idosch.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Petr Machata <petrm@mellanox.com>,
	netdev@vger.kernel.org, devel@driverdev.osuosl.org,
	bridge@lists.linux-foundation.org, f.fainelli@gmail.com,
	andrew@lunn.ch, nikolay@cumulusnetworks.com,
	gregkh@linuxfoundation.org, vivien.didelot@savoirfairelinux.com,
	idosch@mellanox.com, jiri@mellanox.com,
	razvan.stefanescu@nxp.com, davem@davemloft.net
Subject: Re: [PATCH net-next v3 0/7] net: bridge: Notify about bridge VLANs
Date: Tue, 29 May 2018 13:58:53 +0300	[thread overview]
Message-ID: <20180529105853.GA13795@splinter.mtl.com> (raw)
In-Reply-To: <20180529104609.jqbql6ts2rbb7k3l@mwanda>

On Tue, May 29, 2018 at 01:46:09PM +0300, Dan Carpenter wrote:
> It occured to me that I should read the cover letter and here are the
> answers I was looking for.  But the cover letter isn't saved after the
> commits are merged.

DaveM adds the cover letter to the merge commit.

  reply	other threads:[~2018-05-29 10:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 15:10 [Bridge] [PATCH net-next v3 0/7] net: bridge: Notify about bridge VLANs Petr Machata
2018-05-28 15:10 ` Petr Machata
2018-05-28 15:10 ` [Bridge] [PATCH net-next v3 1/7] net: bridge: Extract boilerplate around switchdev_port_obj_*() Petr Machata
2018-05-28 15:10   ` Petr Machata
2018-05-29 10:35   ` [Bridge] " Dan Carpenter
2018-05-29 10:35     ` Dan Carpenter
2018-05-29 12:42   ` [Bridge] " Vivien Didelot
2018-05-29 12:42     ` Vivien Didelot
2018-05-28 15:10 ` [Bridge] [PATCH net-next v3 2/7] mlxsw: spectrum_switchdev: Ignore bridge VLAN events Petr Machata
2018-05-28 15:10   ` Petr Machata
2018-05-29 10:43   ` [Bridge] " Dan Carpenter
2018-05-29 10:43     ` Dan Carpenter
2018-05-28 15:10 ` [Bridge] [PATCH net-next v3 3/7] rocker: rocker_main: " Petr Machata
2018-05-28 15:10   ` Petr Machata
2018-05-28 15:10 ` [Bridge] [PATCH net-next v3 4/7] dsa: port: " Petr Machata
2018-05-28 15:10   ` Petr Machata
2018-05-28 15:10 ` [Bridge] [PATCH net-next v3 5/7] staging: fsl-dpaa2: ethsw: " Petr Machata
2018-05-28 15:10   ` Petr Machata
2018-05-28 15:11 ` [Bridge] [PATCH net-next v3 6/7] net: bridge: Notify about bridge VLANs Petr Machata
2018-05-28 15:11   ` Petr Machata
2018-05-29 10:55   ` [Bridge] " Dan Carpenter
2018-05-29 10:55     ` Dan Carpenter
2018-05-29 13:12     ` [Bridge] " Petr Machata
2018-05-29 13:12       ` Petr Machata
2018-05-28 15:11 ` [Bridge] [PATCH net-next v3 7/7] mlxsw: spectrum_switchdev: Schedule respin during trans prepare Petr Machata
2018-05-28 15:11   ` Petr Machata
2018-05-29 10:46 ` [Bridge] [PATCH net-next v3 0/7] net: bridge: Notify about bridge VLANs Dan Carpenter
2018-05-29 10:46   ` Dan Carpenter
2018-05-29 10:58   ` Ido Schimmel [this message]
2018-05-29 10:58     ` Ido Schimmel
2018-05-29 11:02     ` [Bridge] " Dan Carpenter
2018-05-29 11:02       ` Dan Carpenter

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=20180529105853.GA13795@splinter.mtl.com \
    --to=idosch@idosch.org \
    --cc=andrew@lunn.ch \
    --cc=bridge@lists.linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=petrm@mellanox.com \
    --cc=razvan.stefanescu@nxp.com \
    --cc=vivien.didelot@savoirfairelinux.com \
    /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.