public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	Mark Allyn <mark.a.allyn@intel.com>,
	Alan Cox <alan@linux.intel.com>,
	Ben Hutchings <ben@decadent.org.uk>,
	Joe Perches <joe@perches.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: sep: Fix sparse warning 'do-while statement is not a compound statement'
Date: Wed, 1 Dec 2010 14:52:14 -0800	[thread overview]
Message-ID: <20101201225214.GA15796@kroah.com> (raw)
In-Reply-To: <1291066280-19126-1-git-send-email-peterhuewe@gmx.de>

On Mon, Nov 29, 2010 at 10:31:18PM +0100, Peter Huewe wrote:
> This patch fixes the warning generated by sparse: 'do-while statement is
> not a compound statement' by adding the necessary brackets around the do
> block

This, and your other patches, no longer apply to the linux-next tree.

Care to redo them (and get the description right for the 3/3 patch) and
resend them?

thanks,

greg k-h

  parent reply	other threads:[~2010-12-01 22:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 21:31 [PATCH 1/3] staging/sep: Fix sparse warning 'do-while statement is not a compound statement' Peter Huewe
2010-11-29 21:31 ` [PATCH 2/3] staging/sep: Fix sparse warning 'Using plain integer as NULL pointer' Peter Huewe
2010-11-29 21:31 ` [PATCH 3/3] staging/sep: Fix sparse printk format warning Peter Huewe
2010-11-29 21:49   ` Randy Dunlap
2010-11-29 21:59     ` Peter Hüwe
2010-11-29 22:01       ` Randy Dunlap
2010-11-29 23:18         ` Jiri Slaby
2010-12-01 22:52 ` Greg KH [this message]
2010-12-01 23:43   ` [PATCH 1/3] staging/sep: Fix sparse warning 'do-while statement is not a compound statement' Peter Huewe
2010-12-01 23:43   ` [PATCH 2/3] staging/sep: Fix sparse warning 'Using plain integer as NULL pointer' Peter Huewe
2010-12-01 23:43   ` [PATCH 3/3] staging/sep: Fix printk format warning Peter Huewe

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=20101201225214.GA15796@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@linux.intel.com \
    --cc=ben@decadent.org.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.a.allyn@intel.com \
    --cc=peterhuewe@gmx.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