From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
kuba@kernel.org, netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-can@vger.kernel.org
Subject: Re: [PATCH net-next v3 1/2] can-isotp: implement cleanups / improvements from review
Date: Mon, 12 Oct 2020 10:30:06 +0200 [thread overview]
Message-ID: <2c57194d-ce05-7a5b-02fa-a8fe776cb467@pengutronix.de> (raw)
In-Reply-To: <15d1b847-d717-7f85-af3f-aaaeef28bd6d@hartkopp.net>
[-- Attachment #1.1: Type: text/plain, Size: 1495 bytes --]
On 10/12/20 10:11 AM, Oliver Hartkopp wrote:
>
>
> On 12.10.20 10:05, Marc Kleine-Budde wrote:
>> On 10/12/20 9:43 AM, Oliver Hartkopp wrote:
>>> As pointed out by Jakub Kicinski here:
>>> http://lore.kernel.org/r/20201009175751.5c54097f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com
>>> this patch addresses the remarked issues:
>>>
>>> - remove empty line in comment
>>> - remove default=y for CAN_ISOTP in Kconfig
>>> - make use of pr_notice_once()
>>> - use GFP_ATOMIC instead of gfp_any() in soft hrtimer context
>>>
>>> The version strings in the CAN subsystem are removed by a separate patch.
>>>
>>> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
>>> ---
>>
>> Added both to linux-can-next.
>
> The patches were intended for 'net-next' as the merge window will open
> *very* soon.
>
> I'm not sure if there would be another pull from linux-can-next until
> then, therefore I would suggest that Jakub takes the patches himself.
I don't mind. FWIW, here's the pull request:
http://lore.kernel.org/r/20201012082727.2338859-1-mkl@pengutronix.de
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-5.10-20201012
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-12 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 7:43 [PATCH net-next v3 1/2] can-isotp: implement cleanups / improvements from review Oliver Hartkopp
2020-10-12 7:43 ` [PATCH net-next v3 2/2] can: remove obsolete version strings Oliver Hartkopp
2020-10-12 8:05 ` [PATCH net-next v3 1/2] can-isotp: implement cleanups / improvements from review Marc Kleine-Budde
2020-10-12 8:11 ` Oliver Hartkopp
2020-10-12 8:30 ` Marc Kleine-Budde [this message]
2020-10-12 8:35 ` 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=2c57194d-ce05-7a5b-02fa-a8fe776cb467@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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.