patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Taekyung Kim <kim.tae.kyung@navercorp.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Ali Alnubani <alialnu@nvidia.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>, "Pei, Andy" <andy.pei@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Wang, Xiao W" <xiao.w.wang@intel.com>,
	"Xia, Chenbo" <chenbo.xia@intel.com>
Subject: Re: [PATCH v4] vdpa/ifc: fix update_datapath error handling
Date: Thu, 10 Nov 2022 18:45:25 +0900	[thread overview]
Message-ID: <Y2zINVHqRkJwKbQx@dev-tkkim-git-send-email-ncl.nfra.io> (raw)
In-Reply-To: <CAJFAV8x4QVF93ajoQPGv1vS8MCPwxaELeWZ5xpbg+0F-ELxmWw@mail.gmail.com>

On Thu, Nov 10, 2022 at 10:38:55AM +0100, David Marchand wrote:
> On Thu, Nov 10, 2022 at 10:34 AM Ali Alnubani <alialnu@nvidia.com> wrote:
> > > > I think the mail for v4 is lost.
> > > > Whenever I send a patch, I received "Your message to dev awaits
> > > moderator approval"
> > > > from dev-owner@dpdk.org with the reason "Post by non-member to a
> > > members-only list".
> > > > Maybe, the reason is that this is the first time that I submit a patch.
> > >
> > > No, I don't think subscription is needed, there should be another issue.
> > > Ali & Thomas, any idea why it happens?
> > >
> >
> > Hello,
> >
> > Subscription to the dev mailing list is required for posting without moderator approval.
> > I see that Taekyung is a member only since Nov 08. Postings prior to his subscription are waiting moderation.
> 
> Indeed, I just flushed the queue.
> 
> 
> -- 
> David Marchand
> 

Hello,

I fully understand what was the problem. It was my mistake.
I will be more cautious before sending a patch.
Thanks for your detailed explanation.

Thanks,
Taekyung

  reply	other threads:[~2022-11-10  9:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <68eacb2c-4004-1f43-f14c-702bcec9fe6f@redhat.com>
2022-11-07  5:34 ` [PATCH v2] " Taekyung Kim
2022-11-07  8:59   ` [PATCH v3] " Taekyung Kim
2022-11-08  1:46     ` Xia, Chenbo
2022-11-08  7:30       ` Taekyung Kim
2022-11-08  7:39       ` Pei, Andy
2022-11-08  7:56         ` Xia, Chenbo
2022-11-08  8:27           ` Taekyung Kim
2022-11-08  8:56           ` [PATCH v4] " Taekyung Kim
2022-11-08 13:49             ` Maxime Coquelin
2022-11-09 10:45               ` Taekyung Kim
2022-11-09  2:39             ` Pei, Andy
2022-11-09 10:47               ` Taekyung Kim
2022-11-10  1:53             ` Xia, Chenbo
2022-11-10  4:02               ` Taekyung Kim
2022-11-10  9:20                 ` Maxime Coquelin
2022-11-10  9:34                   ` Ali Alnubani
2022-11-10  9:38                     ` David Marchand
2022-11-10  9:45                       ` Taekyung Kim [this message]
2022-11-10  9:42                     ` Maxime Coquelin
2022-11-10  4:09               ` [PATCH v5] " Taekyung Kim
2022-11-10  6:12                 ` Xia, Chenbo
2022-11-10  7:02                 ` Xia, Chenbo

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=Y2zINVHqRkJwKbQx@dev-tkkim-git-send-email-ncl.nfra.io \
    --to=kim.tae.kyung@navercorp.com \
    --cc=alialnu@nvidia.com \
    --cc=andy.pei@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xiao.w.wang@intel.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).