From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, sashal@kernel.org,
linux-can@vger.kernel.org, lukas.magel@posteo.net,
patches@lists.linux.dev, maxime.jayat@mobile-devices.fr,
mkl@pengutronix.de, michal.sojka@cvut.cz
Subject: Re: [PATCH] can: isotp: upgrade 5.15 LTS to latest 6.6 mainline code base
Date: Mon, 30 Oct 2023 14:40:54 +0100 [thread overview]
Message-ID: <042cd67b-090c-4705-9a80-b322e7d4e639@hartkopp.net> (raw)
In-Reply-To: <2023103038-spinning-uncooked-b608@gregkh>
On 30.10.23 13:42, Greg KH wrote:
> 20 patches is trivial for us to handle, please do it that way as it
> ensures we keep the proper history, AND we know what to backport when in
> the future.
Ok, will do.
> When you try to crunch patches together, or do non-upstream changes,
> 90%+ of the time they end up being wrong or impossible to maintain over
> time.
Ok, then I will maintain the entire history of fixes of fixes without
crunching them together.
>>> But why just 5.15? What about 6.1.y and 6.5.y?
>>
>> I have posted 5.10 and 5.15 for now.
>> 6.1 would be only this patch
>> 96d1c81e6a04 ("can: isotp: add module parameter for maximum pdu size")
>> I can also provide.
>
> Why add new features to older kernels? That's not going to be ok,
> sorry.
I will drop the module parameter stuff then, as it has no impact on the
communication state machine that is in the focus to be consistently
fixed and updated to the 6.6 code base. Then everything in 5.15 and 5.10
will be on the same level as 6.1. This will ease further fixes and
maintenance.
Best regards,
Oliver
prev parent reply other threads:[~2023-10-30 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 11:31 [PATCH] can: isotp: upgrade 5.15 LTS to latest 6.6 mainline code base Oliver Hartkopp
2023-10-30 11:38 ` Greg KH
2023-10-30 12:09 ` Oliver Hartkopp
2023-10-30 12:42 ` Greg KH
2023-10-30 13:40 ` Oliver Hartkopp [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=042cd67b-090c-4705-9a80-b322e7d4e639@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-can@vger.kernel.org \
--cc=lukas.magel@posteo.net \
--cc=maxime.jayat@mobile-devices.fr \
--cc=michal.sojka@cvut.cz \
--cc=mkl@pengutronix.de \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).