Re: [virtio-dev] Re: [virtio-comment] [RFC PATCH v2 1/1] virtio-can: Device specification - 2nd RFC draft.

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

 



On 07.06.2023 15:45:33, Harald Mommer wrote:
> > > - Removal of priorities and config space. Priorities cannot be supported
> > >    using SocketCAN, the information delivered in the config space cannot
> > >    be determined using SocketCAN. Support of different priorities was
> > >    anyway too much for a first version of a specification. If priorities
> > >    are supported in a future version there will probably be only 2
> > >    different priorities, normal and high. In a future version of the
> > >    specification high priority messages may either be supported by using
> > >    a flag bit in the TX message but most probably the better solution
> > >    will be to add add a dedicated 2nd TX queue for high priority messages
> > >    in a review comment. But as already said priorities are not for now.
> > Please keep the change log separate from the description.
> > 
> > [Most people add a S-o-b, although we don't enforce DCO.]
> 
> I understand neither "S-o-b" nor "DCO". Neither Wikipedia nor Google are
> helpful, nothing fits.

S-o-b: Signed-off-by
DCO: Developer's Certificate of Origin

See https://elixir.bootlin.com/linux/v6.3/source/Documentation/process/submitting-patches.rst#L379

regards,
Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde          |
Embedded Linux                   | https://www.pengutronix.de |
Vertretung Nürnberg              | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-9   |

Attachment: signature.asc
Description: PGP signature


[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