From: Joerg Roedel <jroedel@suse.de>
To: Thierry Reding <treding@nvidia.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
iommu@lists.linux.dev
Subject: Re: [PATCH] iommu/of: mark an unused function as __maybe_unused
Date: Thu, 16 Feb 2023 10:19:03 +0100 [thread overview]
Message-ID: <Y+31B7SN+IUgdWxC@suse.de> (raw)
In-Reply-To: <Y+TO0yEdUNzWUUrA@orome>
On Thu, Feb 09, 2023 at 11:45:39AM +0100, Thierry Reding wrote:
> Maybe this is one of those cases where we should wrap after the return
> type/attributes to keep this somewhat readable?
>
> Either way:
>
> Reviewed-by: Thierry Reding <treding@nvidia.com>
Wrapped it around and applied the patch, thanks.
Regards,
--
Jörg Rödel
jroedel@suse.de
SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
prev parent reply other threads:[~2023-02-16 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 1:03 [PATCH] iommu/of: mark an unused function as __maybe_unused Randy Dunlap
2023-02-09 10:45 ` Thierry Reding
2023-02-16 9:19 ` Joerg Roedel [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=Y+31B7SN+IUgdWxC@suse.de \
--to=jroedel@suse.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=treding@nvidia.com \
--cc=will@kernel.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