On Wed, Apr 10, 2013 at 08:07:41AM -0700, James Bottomley wrote:
> On Wed, 2013-04-10 at 16:52 +0200, Borislav Petkov wrote:
> > On Wed, Apr 10, 2013 at 07:35:58AM -0700, Joe Perches wrote:
> > > or maybe exclude drivers/scsi and include/scsi/
> >
> > and arch/x86/kvm/emulate.c
>
> Actually, we g
On Wed, 2013-04-10 at 16:52 +0200, Borislav Petkov wrote:
> On Wed, Apr 10, 2013 at 07:35:58AM -0700, Joe Perches wrote:
> > or maybe exclude drivers/scsi and include/scsi/
>
> and arch/x86/kvm/emulate.c
Actually, we get this all over drivers. Some of the problems are to do
with the fact that th
On Wed, Apr 10, 2013 at 07:35:58AM -0700, Joe Perches wrote:
> or maybe exclude drivers/scsi and include/scsi/
and arch/x86/kvm/emulate.c
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-s
On Wed, 2013-04-10 at 14:26 +0100, Andy Whitcroft wrote:
> On Tue, Apr 09, 2013 at 02:50:54PM -0700, James Bottomley wrote:
> > It's making checkpatch unusable on most drivers because it's spewing
> > tons of bogus warnings. The problem is the assumption that studly caps
> > is always wrong: it is
On Tue, Apr 09, 2013 at 02:50:54PM -0700, James Bottomley wrote:
> It's making checkpatch unusable on most drivers because it's spewing
> tons of bogus warnings. The problem is the assumption that studly caps
> is always wrong: it isn't if the variables are named after the various
> conventions in
It's making checkpatch unusable on most drivers because it's spewing
tons of bogus warnings. The problem is the assumption that studly caps
is always wrong: it isn't if the variables are named after the various
conventions in the hardware programming guides (which are usually
written by Microsoft
6 matches
Mail list logo
