From: Will Hawkins <hawkinsw@obs.cr>
To: Christoph Hellwig <hch@infradead.org>
Cc: bpf@ietf.org, bpf@vger.kernel.org
Subject: Re: [Bpf] [PATCH] bpf, docs: Add additional ABI working draft base text
Date: Thu, 19 Oct 2023 22:42:01 -0400 [thread overview]
Message-ID: <CADx9qWhTXgKxBpjY47ufhfs=7Fb+mxGULgXo=JrEyUicZ5JP9g@mail.gmail.com> (raw)
In-Reply-To: <ZTDGPJFegKuwZiOe@infradead.org>
On Thu, Oct 19, 2023 at 2:01 AM Christoph Hellwig <hch@infradead.org> wrote:
>
> A little style nitpick on top of all the useful comments from
> David:
>
> > +An application binary interface (ABI) defines the requirements that one or more binary software
>
> Text documents and any other bulky texts should be spaces to 80
> characters. This should just be a very trivial reformat.
Thank you!
As you can tell, I got a little busy with teaching. I plan on spending
time with this tomorrow afternoon and a further revision should be on
its way then. Sorry for the delay!
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Hawkins <hawkinsw@obs.cr>
To: Christoph Hellwig <hch@infradead.org>
Cc: bpf@ietf.org, bpf@vger.kernel.org
Subject: Re: [Bpf] [PATCH] bpf, docs: Add additional ABI working draft base text
Date: Thu, 19 Oct 2023 22:42:01 -0400 [thread overview]
Message-ID: <CADx9qWhTXgKxBpjY47ufhfs=7Fb+mxGULgXo=JrEyUicZ5JP9g@mail.gmail.com> (raw)
Message-ID: <20231020024201.FgUNI8hwFF1atGKGnR0wFG8orpmkwdV3-L8X9qU0vJY@z> (raw)
In-Reply-To: <ZTDGPJFegKuwZiOe@infradead.org>
On Thu, Oct 19, 2023 at 2:01 AM Christoph Hellwig <hch@infradead.org> wrote:
>
> A little style nitpick on top of all the useful comments from
> David:
>
> > +An application binary interface (ABI) defines the requirements that one or more binary software
>
> Text documents and any other bulky texts should be spaces to 80
> characters. This should just be a very trivial reformat.
Thank you!
As you can tell, I got a little busy with teaching. I plan on spending
time with this tomorrow afternoon and a further revision should be on
its way then. Sorry for the delay!
Will
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2023-10-20 2:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:19 [PATCH] bpf, docs: Add additional ABI working draft base text Will Hawkins
2023-10-02 14:19 ` [Bpf] " Will Hawkins
2023-10-03 18:26 ` David Vernet
2023-10-03 18:26 ` [Bpf] " David Vernet
2023-10-21 23:13 ` Will Hawkins
2023-10-21 23:13 ` [Bpf] " Will Hawkins
2023-10-21 23:26 ` [PATCH v2] " Will Hawkins
2023-10-21 23:26 ` [Bpf] " Will Hawkins
2023-10-24 0:55 ` [PATCH] " David Vernet
2023-10-24 0:55 ` [Bpf] " David Vernet
2023-10-24 4:02 ` Christoph Hellwig
2023-10-24 4:02 ` Christoph Hellwig
2023-11-03 21:14 ` Will Hawkins
2023-11-03 21:14 ` Will Hawkins
2023-11-03 21:20 ` [PATCH v3] " Will Hawkins
2023-11-03 21:20 ` [Bpf] " Will Hawkins
2023-11-05 9:51 ` Alexei Starovoitov
2023-11-05 9:51 ` Alexei Starovoitov
2023-11-06 0:17 ` Will Hawkins
2023-11-06 0:17 ` Will Hawkins
2023-11-06 8:38 ` Alexei Starovoitov
2023-11-06 8:38 ` Alexei Starovoitov
2023-11-07 19:56 ` Will Hawkins
2023-11-07 19:56 ` Will Hawkins
2023-11-08 1:17 ` Alexei Starovoitov
2023-11-08 1:17 ` Alexei Starovoitov
2023-11-08 10:13 ` Will Hawkins
2023-11-08 10:13 ` Will Hawkins
2023-11-08 19:51 ` Alexei Starovoitov
2023-11-08 19:51 ` Alexei Starovoitov
2023-11-08 23:57 ` Will Hawkins
2023-11-08 23:57 ` Will Hawkins
2023-11-09 18:31 ` Alexei Starovoitov
2023-11-09 18:31 ` Alexei Starovoitov
2023-11-10 0:56 ` Will Hawkins
2023-11-10 0:56 ` Will Hawkins
2023-11-10 1:35 ` Will Hawkins
2023-11-10 1:35 ` Will Hawkins
2023-10-19 6:01 ` [Bpf] [PATCH] " Christoph Hellwig
2023-10-19 6:01 ` Christoph Hellwig
2023-10-20 2:42 ` Will Hawkins [this message]
2023-10-20 2:42 ` Will Hawkins
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='CADx9qWhTXgKxBpjY47ufhfs=7Fb+mxGULgXo=JrEyUicZ5JP9g@mail.gmail.com' \
--to=hawkinsw@obs.cr \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=hch@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).