Re: [PATCH net-next v3 1/2] can-isotp: implement cleanups / improvements from review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 12.10.20 10:30, Marc Kleine-Budde wrote:
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@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxx>
---

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@xxxxxxxxxxxxxx

     git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-5.10-20201012

Marc

:-D

Well thanks!

I just got the feeling that especially the
"remove default=y for CAN_ISOTP in Kconfig"
issue is urgent in net-next.

So now any way to get the patches is fine.

Thanks & BR,
Oliver



[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux