From: Greg KH <gregkh@linuxfoundation.org>
To: Jimmy Assarsson <jimmyassarsson@gmail.com>
Cc: stable@vger.kernel.org, linux-can@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
Jimmy Assarsson <extja@kvaser.com>
Subject: Re: [PATCH 4.14 1/4] can: kvaser_usb: Add struct kvaser_usb_dev_cfg
Date: Tue, 12 Jul 2022 21:18:25 +0200 [thread overview]
Message-ID: <Ys3JAReeZCbv+vbt@kroah.com> (raw)
In-Reply-To: <5059cce9-76b4-b19c-2d97-c1e54c7dd87d@gmail.com>
On Sun, Jul 10, 2022 at 08:40:30PM +0200, Jimmy Assarsson wrote:
> On 7/10/22 16:21, Greg KH wrote:
> > On Fri, Jul 08, 2022 at 08:46:50PM +0200, Jimmy Assarsson wrote:
> > > Add struct kvaser_usb_dev_cfg to ease backporting of upstream commits:
> > > 49f274c72357 (can: kvaser_usb: replace run-time checks with struct kvaser_usb_driver_info)
> > > e6c80e601053 (can: kvaser_usb: kvaser_usb_leaf: fix CAN clock frequency regression)
> > > b3b6df2c56d8 (can: kvaser_usb: kvaser_usb_leaf: fix bittiming limits)
> >
> > What upstream commit is this from?
>
> Hi Greg,
>
> The original upstream commit introducing struct kvaser_usb_dev_cfg is
> 7259124eac7d1b76b41c7a9cb2511a30556deebe
> can: kvaser_usb: Split driver into kvaser_usb_core.c and kvaser_usb_leaf.c
> And was first merged to 4.19.
>
> This was part of a major restructure of the driver to add support for new type of devices.
Then why not just take thos commits, _OR_ rework the bugfixes to handle
the old style of drivers?
Doing this type of major change that is not directly upstream is almost
always a big mistake as it's not tested well and diverges from what is
in Linus's tree.
Please try to rework these two series and resubmit.
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-12 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 18:46 [PATCH 4.14 0/4] can: kvaser_usb: CAN clock frequency regression Jimmy Assarsson
2022-07-08 18:46 ` [PATCH 4.14 1/4] can: kvaser_usb: Add struct kvaser_usb_dev_cfg Jimmy Assarsson
2022-07-10 14:21 ` Greg KH
2022-07-10 18:40 ` Jimmy Assarsson
2022-07-12 19:18 ` Greg KH [this message]
2022-07-08 18:46 ` [PATCH 4.14 2/4] can: kvaser_usb: replace run-time checks with struct kvaser_usb_driver_info Jimmy Assarsson
2022-07-08 18:46 ` [PATCH 4.14 3/4] can: kvaser_usb: fix CAN clock frequency regression Jimmy Assarsson
2022-07-08 18:46 ` [PATCH 4.14 4/4] can: kvaser_usb: fix bittiming limits Jimmy Assarsson
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=Ys3JAReeZCbv+vbt@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=extja@kvaser.com \
--cc=jimmyassarsson@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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 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.