public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux•vnet.ibm.com>
To: Mauro Carvalho Chehab <mchehab@redhat•com>
Cc: Randy Dunlap <randy.dunlap@oracle•com>,
	srinivasa.deevi@conexant•com, linux-media@vger•kernel.org,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-next <linux-next@vger•kernel.org>,
	sachinp <sachinp@linux•vnet.ibm.com>,
	linux-kernel <linux-kernel@vger•kernel.org>,
	Alexander Beregalov <a.beregalov@gmail•com>
Subject: Re: [BUILD FAILURE 04/04] Next April 21 : x86_64 randconfig [drivers/built-in.o]
Date: Wed, 22 Apr 2009 19:40:18 +0530	[thread overview]
Message-ID: <1240409418.26824.0.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <20090421140847.509f8c59@pedra.chehab.org>

On Tue, 2009-04-21 at 14:08 -0300, Mauro Carvalho Chehab wrote:
> On Tue, 21 Apr 2009 22:22:08 +0530
> Subrata Modak <subrata@linux•vnet.ibm.com> wrote:
> 
> > Observed the following build error. Reported this on 8th and 14th April
> > Next build errors:
> > 
> > http://lkml.org/lkml/2009/4/14/473,
> > 
> > Patch was already provided by Randy on 7th April. This is still to hit
> > the tree:
> > http://lkml.org/lkml/2009/4/7/400,
> > 
> 
> Probably Stephen picked from my tree before I merge this patch on my linux-next tree:
> 
> http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-next.git;a=commit;h=c4f0ad35d1df1fed5fae477f806aa8daf5545520
> 
> This error should disappear on the today's build.

Great. Thanks.

--Subrata

> 

      reply	other threads:[~2009-04-22 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 16:52 [BUILD FAILURE 04/04] Next April 21 : x86_64 randconfig [drivers/built-in.o] Subrata Modak
2009-04-21 17:08 ` Mauro Carvalho Chehab
2009-04-22 14:10   ` Subrata Modak [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=1240409418.26824.0.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux$(echo .)vnet.ibm.com \
    --cc=a.beregalov@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-media@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mchehab@redhat$(echo .)com \
    --cc=randy.dunlap@oracle$(echo .)com \
    --cc=sachinp@linux$(echo .)vnet.ibm.com \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=srinivasa.deevi@conexant$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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