From: Thomas Monjalon <thomas@monjalon.net>
To: fengchengwen <fengchengwen@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Fwd: [dpdk] Patch notification: 6 patches updated
Date: Tue, 03 Aug 2021 16:57:05 +0200 [thread overview]
Message-ID: <3238861.uS1i72r7b6@thomas> (raw)
In-Reply-To: <6feabcbb-bcef-e6bb-1a57-7af031f8552b@huawei.com>
03/08/2021 15:19, fengchengwen:
> On 2021/8/3 20:59, Thomas Monjalon wrote:
> > 03/08/2021 14:54, fengchengwen:
> >> Hi, Thomas
> >>
> >> Why the dmadev patchset v12/13 both deferred ? Does it have anything to do with
> >> the completion of 21.08?
> >
> > We are fixing the last critical bugs to close 21.08 this week.
> > We don't accept new features.
>
> Got it, thanks
>
> >
> > What did you expect?
> > Do you understand that "Deferred" means *not* for this release?
>
> I think we could merge dmadev in 21.08 because most of the patchset are well-reviewed
> (except 5/6 add guide patch), so we can all do specific driver development in 21.11.
No way we merge a feature after -rc2.
prev parent reply other threads:[~2021-08-03 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <162799320357.19159.5656200653298589362@inbox.dpdk.org>
2021-08-03 12:54 ` fengchengwen
2021-08-03 12:59 ` Thomas Monjalon
2021-08-03 13:19 ` fengchengwen
2021-08-03 14:57 ` Thomas Monjalon [this message]
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=3238861.uS1i72r7b6@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.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;
as well as URLs for NNTP newsgroup(s).