From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Michael Forney <mforney@mforney.org>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] libext2fs: avoid pointer arithmetic on `void *`
Date: Mon, 13 Apr 2020 21:59:08 -0400 [thread overview]
Message-ID: <20200414015908.GD90651@mit.edu> (raw)
In-Reply-To: <8304797A-1199-45A4-818F-1BBE598C73A6@dilger.ca>
On Sun, Apr 05, 2020 at 06:43:09PM -0600, Andreas Dilger wrote:
> On Apr 4, 2020, at 10:53 PM, Michael Forney <mforney@mforney.org> wrote:
> >
> > The pointer operand to the binary `+` operator must be to a complete
> > object type.
> >
> > Signed-off-by: Michael Forney <mforney@mforney.org>
>
> Seems straight forward enough. Not needed for GCC, but strictly correct.
>
> Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Applied, thanks.
- Ted
prev parent reply other threads:[~2020-04-14 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 4:53 [PATCH] libext2fs: avoid pointer arithmetic on `void *` Michael Forney
2020-04-06 0:43 ` Andreas Dilger
2020-04-14 1:59 ` Theodore Y. Ts'o [this message]
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=20200414015908.GD90651@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=mforney@mforney.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).