From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: dev@dpdk.org, Harish Patil <harish.patil@cavium.com>,
Rasesh Mody <rasesh.mody@cavium.com>
Subject: Re: [dpdk-dev] [PATCH dpdk v2] bnx2x: Update firmware versions
Date: Thu, 27 Apr 2017 05:29:04 +0100 [thread overview]
Message-ID: <d4efd46d-0ee2-35c7-d364-d0abad6d384c@intel.com> (raw)
In-Reply-To: <20170427141455.3bf92b09@aik.ozlabs.ibm.com>
On 4/27/2017 5:14 AM, Alexey Kardashevskiy wrote:
> On Wed, 26 Apr 2017 10:18:29 +0100
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
>> On 4/26/2017 9:08 AM, Alexey Kardashevskiy wrote:
>>> Recent kernels/distros have updated firmware images, use them.
>>> In order to keep support of older distros (such as Fedora 19 or
>>> Ubuntu 14.04), this also tries fallback to an order firmware
>>> version.
>>>
>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>> ---
>>> Changes:
>>> v2:
>>> * in addition to the very new firmware images, this adds fallback to
>>> some older firmware present in 3yo distros
>>
>> Hi Alexey,
>>
>> CC'ing maintainers.
>>
>> Thank you for the patch, please CC maintainers in your patches.
>
> Thanks,
>
> for the future - is there anything like kernel's
> scripts/get_maintainer.pl? I could not spot one.
Current process is manually checking MAINTAINERS file.
There is no script, but dpdk maintainers file format is compatible with
get_maintaner.pl, I did able to make one for myself as a wrapper to
Linux script.
>
>
> --
> Alexey
>
next prev parent reply other threads:[~2017-04-27 4:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 8:08 Alexey Kardashevskiy
2017-04-26 9:18 ` Ferruh Yigit
2017-04-27 4:14 ` Alexey Kardashevskiy
2017-04-27 4:29 ` Ferruh Yigit [this message]
2017-04-29 0:31 ` Mody, Rasesh
2017-04-29 5:12 ` Alexey Kardashevskiy
2017-06-28 16:01 ` Ferruh Yigit
2017-06-28 17:05 ` Mody, Rasesh
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=d4efd46d-0ee2-35c7-d364-d0abad6d384c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=aik@ozlabs.ru \
--cc=dev@dpdk.org \
--cc=harish.patil@cavium.com \
--cc=rasesh.mody@cavium.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).