Re: linux-next: block tree build failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 03 Sep 2008 18:27:12 +0200 Tejun Heo <tj@xxxxxxxxxx> wrote:

> Andrew Morton wrote:
> > @@ -674,6 +674,8 @@ static void *disk_seqf_next(struct seq_f
> >  	struct device *dev;
> >  
> >  	(*pos)++;
> > +	if (seqf->private == NULL)
> > +		return NULL;
> >  	dev = class_dev_iter_next(seqf->private);
> >  	if (dev)
> >  		return dev_to_disk(dev);
> 
> Ehh... next can't be called with NULL private.

My computer disagreed ;)

>  Where can I take a look
> at the merged tree?  There have been two separate changes to that area
> of code.  Ad-hoc behavior fix for 2.6.27 and general clean up scheduled
> for 2.6.28 and the two use seqf->private for different purposes.  Maybe
> the two got mixed up?

It's linux-next-20080903
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux