linux-kernel - Re: [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070130085305.d86196e8.rdunlap@xenotime.net>
Date:	Tue, 30 Jan 2007 08:53:05 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Dave Jones <davej@...hat.com>,
	Paul Mundt <lethal@...ux-sh.org>,
	Greg Ungerer <greg_ungerer@...urecomputing.com>,
	linux-kernel@...r.kernel.org, ksummit-2007-discuss@...nk.org
Subject: Re: [Ksummit-2007-discuss] Re: [Ksummit-2006-discuss] 2007 Linux
 Kernel Summit

On Tue, 30 Jan 2007 10:48:45 -0600 James Bottomley wrote:

> On Tue, 2007-01-30 at 10:30 +0000, Christoph Hellwig wrote:
> > On Mon, Jan 29, 2007 at 11:34:21PM -0500, Dave Jones wrote:
> > > It might be worth putting together a list of do's and don'ts for the
> > > CPU architects if we have a panel again this year (and its usually
> > > a fairly popular session, so I'd be surprised if it got dropped).
> > > something along the lines of
> > 
> > Count my vote for dropping the cpu panels session.  It's been far
> > too marketing oriented, and all of the companies have far more interesting
> > meetings of their own where thos caring about a particular architecture
> > (and that includes much more than just the cpu!) can have usefull discussions.
> 
> Well, OK, but the next question is that is some form of panel of
> outsiders still a useful feature?
> 
> Previous panels we've done have been:
> 
>       * Device Drivers - Inputs from vendors trying to get code into the
>         kernel.  I had feedback that this was reasonably useful; the
>         problem is that it tends to be composed of vendors already
>         making a big effort on the open source process and not the ones
>         (like graphics) who aren't.
>       * Customer Panel - inputs from various users deploying linux in
>         their enterprises.  This did tend to degenerate quickly to a
>         list of requirements.
> 
> The one everyone seems to want is chipsets, so is this the one we want
> to shoot for this year?

As usual, "it depends" on the content.  Can we provide them with
sufficient instructions/guidance so that the listeners get the content
that is desired instead of just some pseudo-marketing or requirements
list?  Any of those panels (Customer or CPU) could have been good or bad.


---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/