patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Luca Boccassi <bluca@debian.org>,
	stable@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-stable] [PATCH 18.11] kni: fix ethtool build error on kernel 5.7
Date: Wed, 2 Sep 2020 09:55:08 +0100	[thread overview]
Message-ID: <f9339705-7965-0d14-494a-76d478860434@redhat.com> (raw)
In-Reply-To: <951b51c5a29bb759db4b8df928331c0bb831d15d.camel@debian.org>

On 28/08/2020 13:39, Luca Boccassi wrote:
> On Fri, 2020-08-28 at 13:03 +0100, Kevin Traynor wrote:
>> From Linux kernel 5.7 onwards, commit
>> 894020fdd88c ("PCI/AER: Rationalize error status register clearing")
>> replaces pci_cleanup_aer_uncorrect_error_status() with
>> pci_aer_clear_nonfatal_status().
>>
>> Add compatability for this as it is used for igb.
>>
>> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>> ---
>>  kernel/linux/kni/ethtool/igb/kcompat.h | 5 +++++
>>  1 file changed, 5 insertions(+)
>>
>> diff --git a/kernel/linux/kni/ethtool/igb/kcompat.h b/kernel/linux/kni/ethtool/igb/kcompat.h
>> index 611a5b7c49..f74038b3eb 100644
>> --- a/kernel/linux/kni/ethtool/igb/kcompat.h
>> +++ b/kernel/linux/kni/ethtool/igb/kcompat.h
>> @@ -3965,3 +3965,8 @@ skb_set_hash(struct sk_buff *skb, __u32 hash, __always_unused int type)
>>  #endif
>>  
>> +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5, 7, 0))
>> +#define pci_cleanup_aer_uncorrect_error_status \
>> +	pci_aer_clear_nonfatal_status
>> +#endif
>> +
>>  #endif /* _KCOMPAT_H_ */
> 
> Acked-by: Luca Boccassi <bluca@debian.org>
> 

Thanks Luca, applied.


      reply	other threads:[~2020-09-02  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 12:03 Kevin Traynor
2020-08-28 12:39 ` Luca Boccassi
2020-09-02  8:55   ` Kevin Traynor [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=f9339705-7965-0d14-494a-76d478860434@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bluca@debian.org \
    --cc=ferruh.yigit@intel.com \
    --cc=stable@dpdk.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).