mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Oleksij Rempel <linux@rempel-privat.de>,
	Roland Hieber <r.hieber@pengutronix.de>,
	Oleksij Rempel <o.rempel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v1 2/2] fs/devfs: fix compile warnings
Date: Wed, 17 Oct 2018 11:55:14 +0200	[thread overview]
Message-ID: <1539770114.3688.22.camel@pengutronix.de> (raw)
In-Reply-To: <2900c5d1-e614-d55e-69c8-6082aaf52132@rempel-privat.de>

Am Mittwoch, den 17.10.2018, 11:44 +0200 schrieb Oleksij Rempel:
> This is the list of all warnings:

[...]

> Not sure if make sense to list all of them. Especially if you can see
> from the patch diff, what the patch is doing.

+1 for not polluting the commit message with all this noise. But I
think it would make sense to move the Wmissing-prototypes CFLAG out of
the mips architecture to apply it generally across all architectures,
so we don't introduce any more of those issues without noticing.

Regards,
Lucas


> Am 17.10.2018 um 11:22 schrieb Roland Hieber:
> > For both of these, it would be nice to know what the compiler warnings
> > were, in case anyone wants to grep the logs.
> > 
> >  - Roland
> > 
> > On Tue, Oct 16, 2018 at 09:50:22PM +0200, Oleksij Rempel wrote:
> > > > > > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > > ---
> > >  fs/devfs.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/fs/devfs.c b/fs/devfs.c
> > > index d2b801036e..10f098280e 100644
> > > --- a/fs/devfs.c
> > > +++ b/fs/devfs.c
> > > @@ -193,7 +193,7 @@ static struct inode *devfs_alloc_inode(struct super_block *sb)
> > > > > >  	return &node->inode;
> > >  }
> > >  
> > > -int devfs_iterate(struct file *file, struct dir_context *ctx)
> > > +static int devfs_iterate(struct file *file, struct dir_context *ctx)
> > >  {
> > > > > >  	struct cdev *cdev;
> > >  
> > > -- 
> > > 2.19.0
> > > 
> > > 
> > > _______________________________________________
> > > barebox mailing list
> > > barebox@lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/barebox
> > > 
> 
> 

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-10-17  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 19:50 [PATCH v1 1/2] ratp: " Oleksij Rempel
2018-10-16 19:50 ` [PATCH v1 2/2] fs/devfs: " Oleksij Rempel
2018-10-17  9:22   ` Roland Hieber
2018-10-17  9:44     ` Oleksij Rempel
2018-10-17  9:55       ` Lucas Stach [this message]
2018-10-18  6:59 ` [PATCH v1 1/2] ratp: " Sascha Hauer

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=1539770114.3688.22.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=linux@rempel-privat.de \
    --cc=o.rempel@pengutronix.de \
    --cc=r.hieber@pengutronix.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