mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: Arun Thomas <arun.thomas@gmail.com>,
	Kulikov Vasiliy <segooon@gmail.com>,
	Javier Martinez Canillas <martinez.javier@gmail.com>,
	Gustavo Silva <silvagustavo@users.sourceforge.net>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/comedi/me4000: fix sparse warning "obsolete struct initializer"
Date: Wed, 19 Jan 2011 15:01:20 -0800	[thread overview]
Message-ID: <20110119230120.GB23564@suse.de> (raw)
In-Reply-To: <201101182249.11127.PeterHuewe@gmx.de>

On Tue, Jan 18, 2011 at 10:49:10PM +0100, Peter Hüwe wrote:
> Am Montag 10 Januar 2011, 23:07:16 schrieb Peter Huewe:
> > This patch fixes the sparse warnings in me4000.c:
> > me4000.c:122:1: warning: obsolete struct initializer, use C99 syntax
> > me4000.c:123:1: warning: obsolete struct initializer, use C99 syntax
> > me4000.c:124:1: warning: obsolete struct initializer, use C99 syntax
> > me4000.c:125:1: warning: obsolete struct initializer, use C99 syntax
> > by converting the struct to use C99 syntax
> > 
> > Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
>  Ping - any updates on this one?

I have to wait until .38-rc1 before I can look at these.  Now that it is
out, I hope to get through my huge patch-queue by Friday, before I take
off on another trip...

Actually, that trip does provide a whole lot of uninterrupted plane
time, so that might be a bit better place to do this work...

thanks,

greg k-h

      reply	other threads:[~2011-01-19 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 22:07 Peter Huewe
2011-01-18 21:49 ` Peter Hüwe
2011-01-19 23:01   ` Greg KH [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=20110119230120.GB23564@suse.de \
    --to=gregkh@suse.de \
    --cc=PeterHuewe@gmx.de \
    --cc=arun.thomas@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martinez.javier@gmail.com \
    --cc=segooon@gmail.com \
    --cc=silvagustavo@users.sourceforge.net \
    /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
all inboxes | Powered by JetHome®