From: Saeed Mahameed <saeedm@mellanox.com>
To: "davem@davemloft.net" <davem@davemloft.net>,
"xianfengting221@163.com" <xianfengting221@163.com>,
"leon@kernel.org" <leon@kernel.org>
Cc: "cai@lca.pw" <cai@lca.pw>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"lsahlber@redhat.com" <lsahlber@redhat.com>,
"kw@linux.com" <kw@linux.com>,
"xiubli@redhat.com" <xiubli@redhat.com>,
"airlied@redhat.com" <airlied@redhat.com>,
Moshe Shemesh <moshe@mellanox.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wqu@suse.com" <wqu@suse.com>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
"yamada.masahiro@socionext.com" <yamada.masahiro@socionext.com>,
"stfrench@microsoft.com" <stfrench@microsoft.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] net/mlx5: add the missing space character
Date: Fri, 17 Apr 2020 22:40:08 +0000 [thread overview]
Message-ID: <cc28a4bf79e8edbe4a27fac068ce556e8b9da2da.camel@mellanox.com> (raw)
In-Reply-To: <4861c789-a333-efea-6d51-ab5511645dcf@163.com>
On Fri, 2020-04-17 at 12:34 +0800, Hu Haowen wrote:
> On 2020/4/17 11:44 AM, Saeed Mahameed wrote:
> > On Thu, 2020-04-16 at 22:44 +0800, Hu Haowen wrote:
> > > On 2020/4/9 3:42 AM, Saeed Mahameed wrote:
> > > > On Fri, 2020-04-03 at 12:26 +0800, Hu Haowen wrote:
> > > > > Commit 91b56d8462a9 ("net/mlx5: improve some comments") did
> > > > > not
> > > > > add
> > > > > that missing space character and this commit is used to fix
> > > > > it
> > > > > up.
> > > > >
> > > > > Fixes: 91b56d8462a9 ("net/mlx5: improve some comments")
> > > > >
> > > > Please re-spin and submit to net-next once net-next re-opens,
> > > > avoid referencing the above commit since this patch is a stand
> > > > alone
> > > > and has nothing to do with that patch.. just have a stand alone
> > > > commit
> > > > message explaining the space fix.
> > > Sorry for my late reply. Because I'm a kernel newbie, I know
> > > nothing
> > > about the basic methods and manners in the kernel development.
> > > Thanks
> > > a lot for your patience on my mistake, pointing it out and fixing
> > > it
> > > up.
> > >
> > > Btw, did net-next re-open and did my changes get into the
> > > mainline?
> > >
> > >
> > Normally net-next closes once merge window is open at the end of
> > rc7/rc8 kernel cycle.
> >
> > and reopens on the week of the kernel release, after the merge
> > window
> > is closed (2 weeks after rc7/8 is closed).
> >
> > you can use this link.
> > http://vger.kernel.org/~davem/net-next.html
>
> Oh... Thanks.
>
> But it's more than 2 weeks since Linux 5.6 was released, so net-next
> should be open now according to your words. But it's still closed.
>
> Is my idea wrong? Does "kernel release" mean an -rc release or a
> formal
> release?
Oh, my bad,
yes release means a kernel release .. 5.x
what i meant is when the rc1 is out two weeks after the kernel release.
next prev parent reply other threads:[~2020-04-17 22:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 4:26 Hu Haowen
2020-04-08 19:42 ` Saeed Mahameed
2020-04-16 14:44 ` Hu Haowen
2020-04-17 3:44 ` Saeed Mahameed
2020-04-17 4:34 ` Hu Haowen
2020-04-17 22:40 ` Saeed Mahameed [this message]
2020-04-18 12:54 ` Hu Haowen
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=cc28a4bf79e8edbe4a27fac068ce556e8b9da2da.camel@mellanox.com \
--to=saeedm@mellanox.com \
--cc=airlied@redhat.com \
--cc=cai@lca.pw \
--cc=chris@chris-wilson.co.uk \
--cc=davem@davemloft.net \
--cc=kw@linux.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stfrench@microsoft.com \
--cc=wqu@suse.com \
--cc=xianfengting221@163.com \
--cc=xiubli@redhat.com \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®