> I am not suggesting to remove all comments. Some human readable
> explanation is important as long as the code is developed by humans.
>
> I think that I'll have to accept also the extra comments if you are
> really going to use them to check the consistency by a tool. Or
> if they are really
On Thu 2019-08-22 19:38:01, Andrea Parri wrote:
> On Thu, Aug 22, 2019 at 03:50:52PM +0200, Petr Mladek wrote:
> > On Wed 2019-08-21 07:46:28, John Ogness wrote:
> > > On 2019-08-20, Sergey Senozhatsky
> > > wrote:
> > > > [..]
> > > >> > + *
> > > >> > + * Memory barrier involvement:
>
On Fri 2019-08-23 14:54:45, Sergey Senozhatsky wrote:
> On (08/21/19 07:46), John Ogness wrote:
> [..]
> > The labels are necessary for the technical documentation of the
> > barriers. And, after spending much time in this, I find them very
> > useful. But I agree that there needs to be a better
On (08/22/19 15:50), Petr Mladek wrote:
[..]
> I could understand that you spend a lot of time on creating the
> labels and that they are somehow useful for you.
>
> But I am not using them and I hope that I will not have to:
>
> + Grepping takes a lot of time, especially over several files.
On (08/21/19 07:46), John Ogness wrote:
[..]
> The labels are necessary for the technical documentation of the
> barriers. And, after spending much time in this, I find them very
> useful. But I agree that there needs to be a better way to assign label
> names.
[..]
> > Where dp stands for
On Thu, Aug 22, 2019 at 03:50:52PM +0200, Petr Mladek wrote:
> On Wed 2019-08-21 07:46:28, John Ogness wrote:
> > On 2019-08-20, Sergey Senozhatsky wrote:
> > > [..]
> > >> > + *
> > >> > + * Memory barrier involvement:
> > >> > + *
> > >> > + * If dB reads from gA, then
On Wed 2019-08-21 07:46:28, John Ogness wrote:
> On 2019-08-20, Sergey Senozhatsky wrote:
> > [..]
> >> > + *
> >> > + * Memory barrier involvement:
> >> > + *
> >> > + * If dB reads from gA, then dC reads from fG.
> >> > + * If dB reads from gA, then dD
On Wed 2019-08-21 07:42:57, John Ogness wrote:
> On 2019-08-20, Petr Mladek wrote:
> >> --- /dev/null
> >> +++ b/kernel/printk/dataring.c
> >> +/**
> >> + * _datablock_valid() - Check if given positions yield a valid data block.
> >> + *
> >> + * @dr: The associated data ringbuffer.
> >>
On 2019-08-20, Sergey Senozhatsky wrote:
> [..]
>> > + *
>> > + * Memory barrier involvement:
>> > + *
>> > + * If dB reads from gA, then dC reads from fG.
>> > + * If dB reads from gA, then dD reads from fH.
>> > + * If dB reads from gA, then dE reads from fE.
>> > + *
>> > + *
On 2019-08-20, Petr Mladek wrote:
>> --- /dev/null
>> +++ b/kernel/printk/dataring.c
>> +/**
>> + * _datablock_valid() - Check if given positions yield a valid data block.
>> + *
>> + * @dr: The associated data ringbuffer.
>> + *
>> + * @head_lpos: The newest data logical position.
>> +
On (08/20/19 10:55), Petr Mladek wrote:
[..]
> > +*
> > +* Memory barrier involvement:
> > +*
> > +* If dB reads from gA, then dC reads from fG.
> > +* If dB reads from gA, then dD reads from fH.
> > +* If dB reads from gA, then dE reads from fE.
> > +*
> > +* Note
On Thu 2019-08-08 00:32:26, John Ogness wrote:
> --- /dev/null
> +++ b/kernel/printk/dataring.c
> +/**
> + * _datablock_valid() - Check if given positions yield a valid data block.
> + *
> + * @dr: The associated data ringbuffer.
> + *
> + * @head_lpos: The newest data logical position.
>
12 matches
Mail list logo