All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH] openrisc: Fix compiler warnings in setup
Date: Sat, 7 Aug 2021 13:49:25 +0900	[thread overview]
Message-ID: <CAAfxs7653w00yKVuRy4K-H3_Pe=WCutB8Tfja-hdh1rG-K+yxA@mail.gmail.com> (raw)
In-Reply-To: <655ef6e0-defb-7467-25df-f9a13ab96694@infradead.org>

On Fri, Aug 6, 2021, 4:32 AM Randy Dunlap <rdunlap@infradead.org> wrote:

> On 8/4/21 8:00 PM, Stafford Horne wrote:
> > This was pointed out with the recent name change of or32_early_setup to
> > or1k_early_setup.  Investigating the file I found a few other warnings
> > so cleaning them up here.
> >
> >      arch/openrisc/kernel/setup.c:220:13: warning: no previous prototype
> for 'or1k_early_setup' [-Wmissing-prototypes]
> >        220 | void __init or1k_early_setup(void *fdt)
> >         |             ^~~~~~~~~~~~~~~~
> >
> > Fix this the missing or1k_early_setup prototype warning by adding an
> > asm/setup.h file to define the prototype.
> >
> >      arch/openrisc/kernel/setup.c:246:13: warning: no previous prototype
> for 'detect_unit_config' [-Wmissing-prototypes]
> >        246 | void __init detect_unit_config(unsigned long upr, unsigned
> long mask,
> >         |             ^~~~~~~~~~~~~~~~~~
> >
> > The function detect_unit_config is not used, just remove it.
> >
> >      arch/openrisc/kernel/setup.c:221: warning: Function parameter or
> member 'fdt' not described in 'or1k_early_setup'
> >
> > Add @fdt docs to the function comment to suppress this warning.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Stafford Horne <shorne@gmail.com>
>
> Hi Stafford,
>
> Does this patch apply to your openrisc tree, but not to
> linux-next?  I get a patch error when trying to apply it
> to linux-next-20210805 and this warning is still present:
>
> ../arch/openrisc/kernel/setup.c:221:13: warning: no previous prototype for
> 'or32_early_setup' [-Wmissing-prototypes]
>    221 | void __init or32_early_setup(void *fdt)
>        |             ^~~~~~~~~~~~~~~~
>
> presumably because some openrisc patches are not yet in linux-next??
>
> thanks.
>

Hi Randy,

Thats right, this patch is on top of my openrisc/for-next branch.  It
should show up in linux-next soon.

The branch is here.


https://github.com/openrisc/linux/commit/19e14f3a81d227f1c8b8d5371de28b3ab3deb556

I put this patch on the branch already. I plan to adjust if any feedback.

-stafford

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20210807/0f8dbb35/attachment.htm>

  reply	other threads:[~2021-08-07  4:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05  3:00 [PATCH] openrisc: Fix compiler warnings in setup Stafford Horne
2021-08-05  3:00 ` [OpenRISC] " Stafford Horne
2021-08-05 19:31 ` Randy Dunlap
2021-08-05 19:31   ` [OpenRISC] " Randy Dunlap
2021-08-07  4:49   ` Stafford Horne [this message]
2021-08-09  1:31 ` Guenter Roeck
2021-08-09  1:31   ` [OpenRISC] " Guenter Roeck
2021-08-09  2:28   ` Randy Dunlap
2021-08-09  2:28     ` [OpenRISC] " Randy Dunlap
2021-08-10 21:13     ` Stafford Horne
2021-08-10 21:13       ` [OpenRISC] " Stafford Horne

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='CAAfxs7653w00yKVuRy4K-H3_Pe=WCutB8Tfja-hdh1rG-K+yxA@mail.gmail.com' \
    --to=shorne@gmail.com \
    --cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.