All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-media@vger.kernel.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 17 (media/dvb)
Date: Fri, 18 Dec 2009 08:50:09 -0200	[thread overview]
Message-ID: <4B2B5E61.1030207@redhat.com> (raw)
In-Reply-To: <20091217095725.d7109149.randy.dunlap@oracle.com>

Randy Dunlap wrote:
> On Thu, 17 Dec 2009 16:58:40 +1100 Stephen Rothwell wrote:
> 
>> Hi all,
>>
>> My usual call for calm: please do not put stuff destined for 2.6.34 into
>> linux-next trees until after 2.6.33-rc1.
>>
>> Changes since 20091216:
> 
> 
> (repeating:)
> 
> drivers/media/dvb/frontends/dib8000.h:104: error: expected expression before '}' token
> drivers/media/dvb/frontends/dib8000.h:104: warning: left-hand operand of comma expression has no effect
> 
>     return CT_SHUTDOWN,
> 
> 
> s/,/;/ and fix indentation.

The affect patch went into for 2.6.33. I haven't noticed this issue before, since it
appears only if DVB_DIB8000 is not defined.

Anyway, I'm adding today a patch for it.

Thanks,
Mauro.

      reply	other threads:[~2009-12-18 10:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17  5:58 linux-next: Tree for December 17 Stephen Rothwell
2009-12-17 17:55 ` linux-next: Tree for December 17 (pci/quirks) Randy Dunlap
2009-12-17 18:59   ` Jesse Barnes
2009-12-18  8:57     ` Cui, Dexuan
2009-12-17 17:57 ` linux-next: Tree for December 17 (media/dvb) Randy Dunlap
2009-12-18 10:50   ` Mauro Carvalho Chehab [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=4B2B5E61.1030207@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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.