From: Aaron Conole <aconole@redhat.com>
To: Yuanhan Liu <yliu@fridaylinux.org>
Cc: dev@dpdk.org, stable@dpdk.org,
"Michał Mirosław" <michal.miroslaw@atendesoftware.pl>,
"Jingjing Wu" <jingjing.wu@intel.com>,
"Luca Boccassi" <bluca@debian.org>
Subject: Re: [dpdk-stable] [PATCH branch-16.11] net/i40e: return errno when interrupt setup fails
Date: Thu, 19 Oct 2017 10:37:57 -0400 [thread overview]
Message-ID: <f7td15jp5iy.fsf@dhcp-25-97.bos.redhat.com> (raw)
In-Reply-To: <20171019140352.GC1545@yliu-home> (Yuanhan Liu's message of "Thu, 19 Oct 2017 22:03:53 +0800")
Yuanhan Liu <yliu@fridaylinux.org> writes:
> On Thu, Oct 19, 2017 at 09:22:30AM -0400, Aaron Conole wrote:
>> From: Michał Mirosław <michal.miroslaw@atendesoftware.pl>
>>
>> Signed-off-by: Michał Mirosław <michal.miroslaw@atendesoftware.pl>
>> Reviewed-by: Jingjing Wu <jingjing.wu@intel.com>
>> ---
>> This is cherry picked from commit d75547718c87 ("net/i40e: return errno
>> when interrupt setup fails") and applies cleanly. This is just a
>> backport request.
>
> Thanks for the backport! A minor note is that for backport commits, we'd
> like to add something like following in the commit log, for back-tracking
> where the backport commit comes from:
>
> [ backported from upstream commit d75547718c873899b7f26616c50df7936a8f45e8 ]
Will do. Since this is just a git cherry-pick, feel free to ignore the
actual patch submitted, and "do the right thing" if it's easier.
I'll follow that form in the future.
> But no worry, I think Luca could handle that while apply. Luca will start
> maintain 16.11 LTS since now (v16.11.4).
Luca++
> --yliu
>>
prev parent reply other threads:[~2017-10-19 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 13:22 Aaron Conole
2017-10-19 14:03 ` Yuanhan Liu
2017-10-19 14:37 ` Aaron Conole [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=f7td15jp5iy.fsf@dhcp-25-97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=michal.miroslaw@atendesoftware.pl \
--cc=stable@dpdk.org \
--cc=yliu@fridaylinux.org \
/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).