From: Leon Romanovsky <leon@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Saeed Mahameed <saeedm@mellanox•com>,
Jason Gunthorpe <jgg@ziepe•ca>,
Doug Ledford <dledford@redhat•com>,
"David S. Miller" <davem@davemloft•net>,
linux-netdev <netdev@vger•kernel.org>,
RDMA mailing list <linux-rdma@vger•kernel.org>
Subject: Re: linux-next: Please add mlx5-next tree
Date: Sun, 17 Jun 2018 21:52:53 +0300 [thread overview]
Message-ID: <20180617185253.GA7393@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20180610054128.GG12407@mtr-leonro.mtl.com>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
On Sun, Jun 10, 2018 at 08:41:28AM +0300, Leon Romanovsky wrote:
> On Fri, Jun 08, 2018 at 07:47:26AM +1000, Stephen Rothwell wrote:
> > Hi Leon,
> >
> > On Wed, 6 Jun 2018 22:25:00 +0300 Leon Romanovsky <leon@kernel•org> wrote:
> > >
> > > Can you please add the branch "mlx5-next" from the following tree to the
> > > linux-next integration tree?
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/
> > >
> > > The mlx5-next branch is used to send shared pull requests to both netdev
> > > and RDMA subsystems and it is worth to have linux-next coverage on it
> > > before.
> >
> > I try hard not to add new trees during the merge window, sorry. If I
> > forget to add it after -rc1 has been released, please remind me.
>
> Thanks Stephen, I'll do.
>
Hi Stephen,
This is reminder.
Thanks
> >
> > --
> > Cheers,
> > Stephen Rothwell
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-06-17 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 19:25 linux-next: Please add mlx5-next tree Leon Romanovsky
2018-06-07 21:47 ` Stephen Rothwell
2018-06-10 5:41 ` Leon Romanovsky
2018-06-17 18:52 ` Leon Romanovsky [this message]
2018-06-17 22:07 ` Stephen Rothwell
2018-06-08 23:19 ` Stephen Hemminger
2018-06-10 5:40 ` Leon Romanovsky
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=20180617185253.GA7393@mtr-leonro.mtl.com \
--to=leon@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dledford@redhat$(echo .)com \
--cc=jgg@ziepe$(echo .)ca \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=saeedm@mellanox$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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