From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Stein <alexander.stein@systec-electronic.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH] c_can: remove obsolete STRICT_FRAME_ORDERING Kconfig option
Date: Mon, 19 May 2014 09:07:36 +0200 [thread overview]
Message-ID: <5379ADB8.5000403@pengutronix.de> (raw)
In-Reply-To: <53691FC2.3080200@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
On 05/06/2014 07:45 PM, Oliver Hartkopp wrote:
> In 2b9aecdce2 ("can: c_can: Disable rx split as workaround") a new Kconfig
> option was introduced as a workaround. The tests performed by Alexander Stein
> confirmed this option to be obsolete with all the other cleanups and fixes
> that had been discussed that time:
> http://marc.info/?l=linux-can&m=139746476821294&w=2
>
> Both (author and tester) agreed to remove this Kconfig option again:
> http://marc.info/?l=linux-can&m=139883820714229&w=2
>
> As some more cleanups took place since then a simple revert is not possible.
> This patch removes the entire option as it would behave when disabled.
> Further beautification’s can be done later.
>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> Tested-by: Alexander Stein <alexander.stein@systec-electronic.com>
Applied to can.
Tnx,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]
prev parent reply other threads:[~2014-05-19 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 17:45 [PATCH] c_can: remove obsolete STRICT_FRAME_ORDERING Kconfig option Oliver Hartkopp
2014-05-19 7:07 ` Marc Kleine-Budde [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=5379ADB8.5000403@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=alexander.stein@systec-electronic.com \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=tglx@linutronix.de \
/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.