All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: saeedb@amazon.com
Cc: netdev@vger.kernel.org, dwmw@amazon.co.uk, zorik@amazon.com,
	matua@amazon.com, msw@amazon.com, aliguori@amazon.com,
	nafea@amazon.com, gtzalik@amazon.com, netanel@amazon.com,
	alisaidi@amazon.com, akiyano@amazon.com
Subject: Re: [PATCH V1 net 0/2] net: ena: race condition bug fix and version update
Date: Wed, 13 Mar 2019 10:52:07 -0700 (PDT)	[thread overview]
Message-ID: <20190313.105207.1428262813866246164.davem@davemloft.net> (raw)
In-Reply-To: <1552481974151.81058@amazon.com>

From: "Bshara, Saeed" <saeedb@amazon.com>
Date: Wed, 13 Mar 2019 12:59:34 +0000

> sorry for the late response. I agree that with stable versions the
> driver version is not good indication for which exact code is
> running.  however, we have many users that port the latest ena
> driver as-is from kernel sources into their older kernels, mainly to
> pull new ENA features (e.g. low latency queues). for those cases,
> the driver version helps us to identify the driver's code, so in
> practice this just works fine.

I will try one more time.

If I push fix X for the ENA driver to -stable and that bumps the version
number, all of the features associated with that version number are not
present in the -stable backport.

It does NOT work.

      reply	other threads:[~2019-03-13 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 17:17 [PATCH V1 net 0/2] net: ena: race condition bug fix and version update akiyano
2019-02-11 17:17 ` [PATCH V1 net 1/2] net: ena: fix race between link up and device initalization akiyano
2019-02-11 17:17 ` [PATCH V1 net 2/2] net: ena: update driver version from 2.0.2 to 2.0.3 akiyano
2019-02-12 11:12   ` Moritz Fischer
2019-02-12 11:42     ` Kiyanovski, Arthur
2019-02-12 13:11       ` Andrew Lunn
2019-02-12 19:06 ` [PATCH V1 net 0/2] net: ena: race condition bug fix and version update David Miller
2019-03-13 12:59   ` Bshara, Saeed
2019-03-13 17:52     ` David Miller [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=20190313.105207.1428262813866246164.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akiyano@amazon.com \
    --cc=aliguori@amazon.com \
    --cc=alisaidi@amazon.com \
    --cc=dwmw@amazon.co.uk \
    --cc=gtzalik@amazon.com \
    --cc=matua@amazon.com \
    --cc=msw@amazon.com \
    --cc=nafea@amazon.com \
    --cc=netanel@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedb@amazon.com \
    --cc=zorik@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.