headers
Sachin Sant | 1 May 2010 11:54
Picon

Re: -next Apr 30: OOPS during eHEA driver initialization

Grant Likely wrote:
> On Fri, Apr 30, 2010 at 11:35 AM, Grant Likely
> <grant.likely <at> secretlab.ca> wrote:
>   
>> On Fri, Apr 30, 2010 at 11:27 AM, Sachin Sant <sachinp <at> in.ibm.com> wrote:
>>     
>>> Sachin Sant wrote:
>>>       
>>>> With today's next eHEA drivers fails to initialize.
>>>>         
>>> If i revert the following patch eHEA network interface is initialized
>>> properly.
>>>
>>> commit cebfe0b6709abdab997c1a00499d67efa32ee1f0
>>> drivercore: Add of_match_table to the common device drivers
>>>       
>> That is an easy one to fix.  I'll get it updated today and send you the result.
>>     
>
> Let me know if this patch fixes it:
>   
Works for me. Thanks Grant. 

Tested-by : Sachin Sant <sachinp <at> in.ibm.com>

Regards
-Sachin

> Cheers,
> g.
(Continue reading)

Permalink | Reply | 0 comments |
headers
@@@ | 2 May 2010 00:11
Picon
Picon

Irish 2010 Grant Winner

This is to inform you that you have been selected for a cash prize of £1,000,000 (British Pounds) held on the 25th
of April.

CLAIM FORM
Names:_____________
Tele:_____________
Age:_________
Address:___
occupation:___
country:___
next of kin:____
Email:redeem_prize <at> live.co.uk

Agent Name: Mr.Mark Foster
Tel:+44 704-571-0545
Permalink | Reply | 0 comments |
headers
Eric W. Biederman | 2 May 2010 06:55

Re: linux-next: build failure after merge of the staging-next tree

Greg KH <greg <at> kroah.com> writes:

> On Fri, Apr 30, 2010 at 03:52:05PM +1000, Stephen Rothwell wrote:
>> Hi Greg,
>> 
>> After merging the staging-next tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>> 
>> drivers/md/md.c: In function 'level_store':
>> drivers/md/md.c:3029: error: too few arguments to function 'sysfs_get_dirent'
>> 
>> Caused by commit 262f8e4937e7b4a587923ca3c039a184668f49ec ("sysfs:
>> Implement sysfs tagged directory support") from the driver-core tree
>> interacting with commit fecc531e3cc0de60514d326c7d82f1075ed55888 ("md:
>> manage redundancy group in sysfs when changing level") from the md.
>> 
>> I have applied this fixup patch for today and can carry it as necessary.
>
> Thanks, that would be great.
>
>> [This could have been avoided, of course, by creating a new API (maybe
>> sysfs_get_dirent_tagged) and implementing the old API in terms of that].
>
> Hm Eric, any thoughts?

I believe I touched all of the users of sysfs_get_dirent outside of sysfs
that existed when I sent you the patch.

Right now using sysfs_get_dirent is a hack to support notifications of
changes to sysfs files from atomic contexts, where sysfs_notify is
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stephen Rothwell | 3 May 2010 02:01
Picon
Picon

linux-next: build warnings after merge of the driver-core.current tree

Hi Greg,

After merging the driver-core.current tree, today's linux-next build (powerpc
ppc64_defconfig and x86_64 allmodconfig) produced these warning:

drivers/pcmcia/ds.c: In function 'pcmcia_load_firmware':
drivers/pcmcia/ds.c:761: warning: passing argument 1 of 'release_firmware' discards qualifiers from
pointer target type
include/linux/firmware.h:46: note: expected 'struct firmware *' but argument is of type 'const struct
firmware *'
drivers/net/cxgb3/cxgb3_main.c: In function 't3_get_edc_fw':
drivers/net/cxgb3/cxgb3_main.c:1084: warning: passing argument 1 of 'release_firmware' discards
qualifiers from pointer target type
include/linux/firmware.h:46: note: expected 'struct firmware *' but argument is of type 'const struct
firmware *'

and *lots* more similar warnings ...

Caused by commit d5ae47f7d90f94a15e668f389c12211a11798b6f
("firmware_class: fix memory leak - free allocated pages").  This patch
was modified from an earlier version that produced different (though many
fewer) warnings.

--

-- 
Cheers,
Stephen Rothwell                    sfr <at> canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
Permalink | Reply | 2 comments |
headers
Stephen Rothwell | 3 May 2010 04:08
Picon
Picon

linux-next: build failure after merge of the net tree

Hi Dave,

After merging the net tree, today's linux-next build (x86_64
allmodconfig) failed like this:

net/sctp/socket.c: In function 'sctp_data_ready':
net/sctp/socket.c:6191: error: implicit declaration of function 'sk_has_sleeper'
net/sctp/socket.c:6192: error: 'struct sock' has no member named 'sk_sleep'

Caused by commit 43815482370c510c569fd18edb57afcb0fa8cab6 ("net:
sock_def_readable() and friends RCU conversion") interacting with commit
561b1733a465cf9677356b40c27653dd45f1ac56 ("sctp: avoid irq lock inversion
while call sk->sk_data_ready()") which entered Linus' tree on April 29.

I have used the net tree from next-20100430 for today.
--

-- 
Cheers,
Stephen Rothwell                    sfr <at> canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
Permalink | Reply | 2 comments |
headers
Stephen Rothwell | 3 May 2010 07:01
Picon
Picon

Re: linux-next: build failure after merge of the v4l-dvb tree

Hi Mauro,

On Wed, 28 Apr 2010 11:07:10 +1000 Stephen Rothwell <sfr <at> canb.auug.org.au> wrote:
>
> On Mon, 12 Apr 2010 12:40:41 +1000 Stephen Rothwell <sfr <at> canb.auug.org.au> wrote:
> >
> > After merging the v4l-dvb tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> > 
> > drivers/input/input.c: In function 'input_default_setkeycode':
> > drivers/input/input.c:691: error: 'keycode' undeclared (first use in this function)
> > 
> > Caused by commit df7ad46fc171965103f02649f6c2f02c6ca8b331 ("Merge branch
> > 'master' of /home/v4l/bare_trees/v4l-dvb").  The merge resolution is not
> > quite right.
> > 
> > I have used the v4l-dvb tree from next-20100409 for today.
> 
> I am still getting this build failure ...

Any chance of it being fixed?
--

-- 
Cheers,
Stephen Rothwell                    sfr <at> canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
Permalink | Reply | 2 comments |
headers
Stephen Rothwell | 3 May 2010 07:16
Picon
Picon

linux-next: Tree for May 3

Hi all,

Changes since 20100430:

Dropped trees: tmio-mmc (long unresolved conflicts and unable to fetch)
	hwlat (at the maintainer's request)

My fixes tree is empty.

The usb.current tree lost its conflict.

The v4l-dvb tree still has its build failure, so I used the version from
next-20100409.

The net tree gained a build failure so I used the version from
next-20100430.

The bk-ioctl tree lost its build failure and 2 conflicts.

The driver-core tree gained a build failure for which I applied a patch.

The usb tree lost two of its build failures bit still has one more for
which I have reverted a commit.

----------------------------------------------------------------------------

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
(Continue reading)

Permalink | Reply | 19 comments |
headers
Stephen Rothwell | 3 May 2010 09:29
Picon
Picon

Re: linux-next: Tree for April 30

Hi Frederic,

On Fri, 30 Apr 2010 21:27:50 +0200 Frederic Weisbecker <fweisbec <at> gmail.com> wrote:
>
> On Fri, Apr 30, 2010 at 04:35:38PM +1000, Stephen Rothwell wrote:
> > 
> > Changes since 20100429:
> > 
> > The bk-ioctl tree still has its build failure so I used the version from
> > next-20100428.
> 
> That looks weird, I fixed all the reported conflicts and build error you
> reported. Or may be there are some others left that I missed in allyesconfig?

That would be because I fetched your tree on Friday before your fixes were
publically available.  It is all ok today, thanks.

--

-- 
Cheers,
Stephen Rothwell                    sfr <at> canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
Permalink | Reply | 0 comments |
headers
Mauro Carvalho Chehab | 3 May 2010 09:58
Favicon

Re: linux-next: build failure after merge of the v4l-dvb tree

Stephen Rothwell wrote:
> Hi Mauro,
> 
> On Wed, 28 Apr 2010 11:07:10 +1000 Stephen Rothwell <sfr <at> canb.auug.org.au> wrote:
>> On Mon, 12 Apr 2010 12:40:41 +1000 Stephen Rothwell <sfr <at> canb.auug.org.au> wrote:
>>> After merging the v4l-dvb tree, today's linux-next build (powerpc
>>> ppc64_defconfig) failed like this:
>>>
>>> drivers/input/input.c: In function 'input_default_setkeycode':
>>> drivers/input/input.c:691: error: 'keycode' undeclared (first use in this function)
>>>
>>> Caused by commit df7ad46fc171965103f02649f6c2f02c6ca8b331 ("Merge branch
>>> 'master' of /home/v4l/bare_trees/v4l-dvb").  The merge resolution is not
>>> quite right.
>>>
>>> I have used the v4l-dvb tree from next-20100409 for today.
>> I am still getting this build failure ...
> 
> Any chance of it being fixed?

Done. 

--

-- 

Cheers,
Mauro
Permalink | Reply | 1 comment |
headers
Stephen Rothwell | 3 May 2010 12:25
Picon
Picon

Re: linux-next: build failure after merge of the v4l-dvb tree

On Mon, 03 May 2010 04:58:30 -0300 Mauro Carvalho Chehab <mchehab <at> infradead.org> wrote:
>
> Done. 

Thanks.

--

-- 
Cheers,
Stephen Rothwell                    sfr <at> canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
Permalink | Reply | 0 comments |

Gmane