linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: [PATCH RESEND iproute2 5.11] iplink_can: add Classical CAN frame LEN8_DLC support
Date: Tue, 2 Feb 2021 08:35:56 -0700	[thread overview]
Message-ID: <586c2310-17ee-328e-189c-f03aae1735e9@gmail.com> (raw)
In-Reply-To: <d8ba08c4-a1c2-78b8-1b09-36c522b07a8c@hartkopp.net>

On 2/2/21 3:48 AM, Oliver Hartkopp wrote:
> 
> Are you sure this patch is correctly assigned to iproute2-next?
> 
> IMO it has to be applied to iproute2 as the functionality is already in
> v5.11 which is in rc6 right now.
> 

new features land in iproute2-next just as they do for the kernel with
net-next.

Patches adding support for kernel features should be sent in the same
development window if you want the iproute2 support to match kernel version.

  reply	other threads:[~2021-02-02 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 10:40 [PATCH RESEND iproute2 5.11] iplink_can: add Classical CAN frame LEN8_DLC support Oliver Hartkopp
2021-02-01 15:21 ` Vincent MAILHOL
     [not found] ` <b835a46c-f950-6c58-f50f-9b2f4fd66b46@gmail.com>
2021-02-02 10:48   ` Oliver Hartkopp
2021-02-02 15:35     ` David Ahern [this message]
2021-02-02 17:30       ` Oliver Hartkopp
2021-02-03 15:47         ` David Ahern
2021-02-03 19:04           ` Oliver Hartkopp
2021-02-04  3:15             ` David Ahern
2021-02-04 20:29               ` Oliver Hartkopp

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=586c2310-17ee-328e-189c-f03aae1735e9@gmail.com \
    --to=dsahern@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=stephen@networkplumber.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).