public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/1] docs: kernel-doc: fix parsing of function pointers
Date: Mon, 8 Oct 2018 14:06:41 -0400	[thread overview]
Message-ID: <20181008180641.GA24778@oliver.ec.rr.com> (raw)
In-Reply-To: <20180903185003.10108-1-xypron.glpk@gmx.de>

On Mon, Sep 03, 2018 at 08:50:03PM +0200, Heinrich Schuchardt wrote:

> kernel-doc fails to parse function definitions like the one below
> 
> efi_status_t efi_create_event(uint32_t type, efi_uintn_t notify_tpl,
> 			      void (EFIAPI *notify_function) (
> 					struct efi_event *event,
> 					void *context),
> 			      void *notify_context, efi_guid_t *group,
> 			      struct efi_event **event)
> {
> 
> due to the "EFIAPI" attribute preceding the function name.
> 
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> I am submitted the same patch to the Kernel upstream:
> https://lkml.org/lkml/2018/9/3/1185

Looking at the lkml thread this seems to have not reached a conclusion.
Are you planning to push some v2 there that tries to address some of the
oddities there?  Or should we just make this a local correction?
Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181008/ea5bc487/attachment.sig>

  reply	other threads:[~2018-10-08 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 18:50 [U-Boot] [PATCH 1/1] docs: kernel-doc: fix parsing of function pointers Heinrich Schuchardt
2018-10-08 18:06 ` Tom Rini [this message]
2018-10-08 23:26   ` [U-Boot] [U-Boot, " Heinrich Schuchardt

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=20181008180641.GA24778@oliver.ec.rr.com \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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