From: Alexey Dobriyan <firstname.lastname@example.org> To: Miguel Ojeda <email@example.com> Cc: Andrew Morton <firstname.lastname@example.org>, linux-kernel <email@example.com>, Miguel Ojeda <firstname.lastname@example.org> Subject: Re: [PATCH] ELF: add and use SUPRESS_WARN_UNUSED_RESULT\ Date: Sat, 26 Jun 2021 09:44:25 +0300 [thread overview] Message-ID: <YNbMyXR476FvEPaA@localhost.localdomain> (raw) In-Reply-To: <CANiq72=HCKAyuLD3anAuSug4s0MKMHwRXdMPt0pNs-mTxD1CXg@mail.gmail.com> On Fri, Jun 25, 2021 at 11:57:21PM +0200, Miguel Ojeda wrote: > On Fri, Jun 25, 2021 at 11:10 PM Alexey Dobriyan <email@example.com> wrote: > > > > This is natural place. If you're supressing WUR, then the WUR macro > > itself is defined implying that the header has been included. > > I am not sure I understand -- I guess you are saying that your macro > is only ever needed if `__must_check` is defined, which is what I > meant by "related". > > But this header was intentionally created to untangle others by > keeping only attributes here. Sure. But then developer needs to include another header to use SUPRESS_WUR. As posted, attribute and its suppressor go hand to hand.
next prev parent reply other threads:[~2021-06-26 6:46 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-25 19:52 [PATCH] ELF: add and use SUPRESS_WARN_UNUSED_RESULT Alexey Dobriyan 2021-06-25 20:34 ` Miguel Ojeda 2021-06-25 21:10 ` Alexey Dobriyan 2021-06-25 21:11 ` Randy Dunlap 2021-06-25 21:57 ` Miguel Ojeda 2021-06-26 6:44 ` Alexey Dobriyan [this message] 2021-06-26 14:29 ` [PATCH] ELF: add and use SUPRESS_WARN_UNUSED_RESULT\ Miguel Ojeda 2021-06-25 21:13 ` [PATCH v2] ELF: add and use SUPPRESS_WARN_UNUSED_RESULT Alexey Dobriyan 2021-06-25 23:30 ` Andrew Morton 2021-06-26 2:05 ` Linus Torvalds 2021-06-26 2:37 ` Al Viro 2021-06-26 3:13 ` Linus Torvalds 2021-06-26 6:40 ` Alexey Dobriyan
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=YNbMyXR476FvEPaA@localhost.localdomain \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] ELF: add and use SUPRESS_WARN_UNUSED_RESULT\' \ /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
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).