From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Theodore Tso <tytso@MIT.EDU>, Greg KH <greg@kroah.com>,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
v4l-dvb-maintainer@linuxtv.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: linux-next: Tree for March 20
Date: Thu, 20 Mar 2008 12:14:59 -0300 [thread overview]
Message-ID: <20080320121459.381e73eb@gaivota> (raw)
In-Reply-To: <20080319212121.9705ca9a.randy.dunlap@oracle.com>
On Wed, 19 Mar 2008 21:21:21 -0700
Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Thu, 20 Mar 2008 14:39:53 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> > (tar balls at
> > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).
>
> gcc doesn't like nested /* comments:
>
> next-20080320/drivers/media/video/bt8xx/bttv-cards.c:3030:38: warning: "/*" within comment
> next-20080320/drivers/media/video/bt8xx/bttv-cards.c:3032:20: warning: "/*" within comment
Andrew already did a patch for this. I'll import on my tree.
>
> ---
> ~Randy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Cheers,
Mauro
next prev parent reply other threads:[~2008-03-20 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 3:39 linux-next: Tree for March 20 Stephen Rothwell
2008-03-20 4:21 ` Randy Dunlap
2008-03-20 15:14 ` Mauro Carvalho Chehab [this message]
2008-03-20 4:57 ` Greg KH
2008-03-20 6:17 ` Stephen Rothwell
2008-03-25 6:48 ` Stephen Rothwell
2008-03-25 7:31 ` Greg KH
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=20080320121459.381e73eb@gaivota \
--to=mchehab@infradead.org \
--cc=dan.j.williams@intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=tytso@MIT.EDU \
--cc=v4l-dvb-maintainer@linuxtv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).