DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] event/octeontx: fix snprintf mempool name overflow
Date: Wed, 25 Apr 2018 15:01:54 +0000	[thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA65E04DB17@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <5845616.Es9UhdVMYk@xps>

> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Wednesday, April 25, 2018 3:56 PM
> To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Cc: dev@dpdk.org; Van Haaren, Harry <harry.van.haaren@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] event/octeontx: fix snprintf mempool name
> overflow
> 
> 25/04/2018 14:54, Van Haaren, Harry:
> >
> > +CC Thomas, would you take this one asap it fixes a build warning with
> Meson/GCC 5.4 on Ubuntu with fortified headers.
> >
> > > > Bugzilla-ID: 28
> > > > Fixes: f874c1eb1519 ("event/octeontx: create and free timer adapter")
> > > >
> > > > Reported-by: Harry van Haaren <harry.van.haaren@intel.com>
> > > > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > >
> > >
> > > Nice one, confirmed as fixed!
> > >
> > > I wasn't aware Bugzilla had a diff view; The patch as attachment is
> viewable
> > > here:
> > > https://dpdk.org/tracker/attachment.cgi?id=5&action=diff
> 
> It's nice :)
> 
> I have update the Bugzilla ticket, especially the field URL
> with the link to see the commit in cgit.

I'm working on documenting a suggested workflow, will include
the steps above.

Thanks!

      reply	other threads:[~2018-04-25 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 13:39 Pavan Nikhilesh
2018-04-23 14:21 ` Van Haaren, Harry
2018-04-25 12:54   ` Van Haaren, Harry
2018-04-25 14:55     ` Thomas Monjalon
2018-04-25 15:01       ` Van Haaren, Harry [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=E923DB57A917B54B9182A2E928D00FA65E04DB17@IRSMSX101.ger.corp.intel.com \
    --to=harry.van.haaren@intel.com \
    --cc=dev@dpdk.org \
    --cc=pbhagavatula@caviumnetworks.com \
    --cc=thomas@monjalon.net \
    /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).