From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Cc: linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH v3 7/7] can: Update contact details
Date: Mon, 25 Jan 2021 11:25:25 +0100 [thread overview]
Message-ID: <e39c4ae6-94df-9162-7357-d125ced72d17@hartkopp.net> (raw)
In-Reply-To: <20210120143723.26483-8-rpalethorpe@suse.com>
On 20.01.21 15:37, Richard Palethorpe wrote:
> socketcan-users appears to be no more.
>
> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
Thanks for the cleanup and the rework, Richard!
Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
(for the entire series)
Best regards,
Oliver
> ---
> testcases/network/can/filter-tests/00_Descriptions.txt | 5 +++--
> testcases/network/can/filter-tests/Makefile | 2 --
> 2 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/testcases/network/can/filter-tests/00_Descriptions.txt b/testcases/network/can/filter-tests/00_Descriptions.txt
> index 55d213456..9623d29a0 100644
> --- a/testcases/network/can/filter-tests/00_Descriptions.txt
> +++ b/testcases/network/can/filter-tests/00_Descriptions.txt
> @@ -6,5 +6,6 @@ information on the CAN network protocol family PF_CAN is contained in
>
> For any issue(s) with CAN tests please write to:
> <ltp@lists.linux.it>
> -<socketcan-users@lists.berlios.de>,
> -Oliver Hartkopp <oliver.hartkopp@volkswagen.de>,
> +Oliver Hartkopp <socketcan@hartkopp.net>
> +Linux-CAN ML <linux-can@vger.kernel.org>
> +
> diff --git a/testcases/network/can/filter-tests/Makefile b/testcases/network/can/filter-tests/Makefile
> index 29aaa3240..bd57c7fff 100644
> --- a/testcases/network/can/filter-tests/Makefile
> +++ b/testcases/network/can/filter-tests/Makefile
> @@ -14,8 +14,6 @@
> # You should have received a copy of the GNU General Public License along
> # with this program; if not, write to the Free Software Foundation, Inc.,
> # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
> -#
> -# Send feedback to <socketcan-users@lists.berlios.de>
>
> top_srcdir ?= ../../../..
>
>
next prev parent reply other threads:[~2021-01-25 10:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 14:37 [PATCH v3 0/7] Convert CAN tests to new LTP API Richard Palethorpe
2021-01-20 14:37 ` [PATCH v3 1/7] API: Add FILE_SCANF to new lib Richard Palethorpe
2021-01-20 14:37 ` [PATCH v3 2/7] can: Add can_common.h for vcan device setup Richard Palethorpe
2021-01-25 10:20 ` Oliver Hartkopp
2021-01-25 10:59 ` Richard Palethorpe
2021-01-26 21:28 ` Petr Vorel
2021-01-27 7:52 ` Oliver Hartkopp
2021-01-27 8:18 ` Richard Palethorpe
2021-01-27 12:13 ` Petr Vorel
2021-01-27 15:07 ` [LTP] " Petr Vorel
2021-01-20 14:37 ` [PATCH v3 3/7] can: Add COPYING with dual license text Richard Palethorpe
2021-01-20 14:37 ` [PATCH v3 4/7] can_filter: Convert to new library Richard Palethorpe
2021-01-20 14:37 ` [PATCH v3 5/7] can_recv_own_msgs: " Richard Palethorpe
2021-01-25 14:29 ` [LTP] " Cyril Hrubis
2021-01-20 14:37 ` [PATCH v3 6/7] can: Remove obsolete test wrapper script Richard Palethorpe
2021-01-25 9:10 ` [LTP] " Petr Vorel
2021-01-20 14:37 ` [PATCH v3 7/7] can: Update contact details Richard Palethorpe
2021-01-25 10:25 ` Oliver Hartkopp [this message]
2021-01-25 14:30 ` [LTP] " Cyril Hrubis
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=e39c4ae6-94df-9162-7357-d125ced72d17@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mkl@pengutronix.de \
--cc=rpalethorpe@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox