On Tue, 17 Jul 2012 13:45:06 +1000 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi Greg, > > After merging the tty tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > drivers/tty/tty_ioctl.c: In function 'set_sgflags': > drivers/tty/tty_ioctl.c:741:9: error: request for member 'c_iflag' in something not a structure or union > drivers/tty/tty_ioctl.c:742:9: error: request for member 'c_oflag' in something not a structure or union > drivers/tty/tty_ioctl.c:743:9: error: request for member 'c_lflag' in something not a structure or union > drivers/tty/tty_ioctl.c:745:10: error: request for member 'c_iflag' in something not a structure or union > drivers/tty/tty_ioctl.c:746:10: error: request for member 'c_lflag' in something not a structure or union > drivers/tty/tty_ioctl.c:749:10: error: request for member 'c_lflag' in something not a structure or union > drivers/tty/tty_ioctl.c:753:10: error: request for member 'c_oflag' in something not a structure or union > drivers/tty/tty_ioctl.c:756:10: error: request for member 'c_iflag' in something not a structure or union > drivers/tty/tty_ioctl.c:757:10: error: request for member 'c_lflag' in something not a structure or union > drivers/tty/tty_ioctl.c:759:15: error: request for member 'c_lflag' in something not a structure or union > drivers/tty/tty_ioctl.c:760:10: error: request for member 'c_cc' in something not a structure or union > drivers/tty/tty_ioctl.c:761:10: error: request for member 'c_cc' in something not a structure or union > > Caused by commit adc8d746caa6 ("tty: move the termios object into the > tty"). Did anyone build test this? :-( It's known not to build. I sent Greg some patches but he wants them versus a different tree. I hope to have that done and tested in the next couple of days, until then I'd suggest you drop the tty tree - in particular because the version you are currently using scribbles on other bits of of memory. Alan -- 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