All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kulikov Vasiliy <segooon@gmail.com>
To: Vipin Mehta <Vipin.Mehta@Atheros.com>
Cc: "kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/14] staging: ath6kl: check return code of get_user
Date: Thu, 16 Sep 2010 12:59:08 +0000	[thread overview]
Message-ID: <20100916125908.GA4491@albatros> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983F2381DB98@SC1EXMB-MBCL.global.atheros.com>

On Wed, Sep 08, 2010 at 22:59 -0700, Vipin Mehta wrote:
> Hi Vasiliy,
>     You mentioned in your email that you were unable to compile the driver. Can you pls reproduce a log of the errors you observed?

vasya@albatros:~/linux$ make allyesconfig && make drivers/staging/ath6kl/
  HOSTCC  scripts/kconfig/conf.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --allyesconfig arch/x86/Kconfig
#
# configuration written to .config
#
scripts/kconfig/conf --silentoldconfig arch/x86/Kconfig
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  UPD     include/generated/utsrelease.h
  CC      kernel/bounds.s
  GEN     include/generated/bounds.h
  CC      arch/x86/kernel/asm-offsets.s
  GEN     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
  LD      drivers/staging/ath6kl/built-in.o

I think there should be more CC ath6kl/*.o lines :)


Thanks,
-- 
Vasiliy

WARNING: multiple messages have this Message-ID (diff)
From: Kulikov Vasiliy <segooon@gmail.com>
To: Vipin Mehta <Vipin.Mehta@Atheros.com>
Cc: "kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/14] staging: ath6kl: check return code of get_user and put_user
Date: Thu, 16 Sep 2010 16:59:08 +0400	[thread overview]
Message-ID: <20100916125908.GA4491@albatros> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983F2381DB98@SC1EXMB-MBCL.global.atheros.com>

On Wed, Sep 08, 2010 at 22:59 -0700, Vipin Mehta wrote:
> Hi Vasiliy,
>     You mentioned in your email that you were unable to compile the driver. Can you pls reproduce a log of the errors you observed?

vasya@albatros:~/linux$ make allyesconfig && make drivers/staging/ath6kl/
  HOSTCC  scripts/kconfig/conf.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --allyesconfig arch/x86/Kconfig
#
# configuration written to .config
#
scripts/kconfig/conf --silentoldconfig arch/x86/Kconfig
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  UPD     include/generated/utsrelease.h
  CC      kernel/bounds.s
  GEN     include/generated/bounds.h
  CC      arch/x86/kernel/asm-offsets.s
  GEN     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
  LD      drivers/staging/ath6kl/built-in.o

I think there should be more CC ath6kl/*.o lines :)


Thanks,
-- 
Vasiliy

  reply	other threads:[~2010-09-16 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05 18:32 [PATCH 04/14] staging: ath6kl: check return code of get_user and put_user Kulikov Vasiliy
2010-09-05 18:32 ` Kulikov Vasiliy
2010-09-09  5:59 ` [PATCH 04/14] staging: ath6kl: check return code of get_user Vipin Mehta
2010-09-09  5:59   ` [PATCH 04/14] staging: ath6kl: check return code of get_user and put_user Vipin Mehta
2010-09-16 12:59   ` Kulikov Vasiliy [this message]
2010-09-16 12:59     ` Kulikov Vasiliy
2010-09-16 13:23     ` [PATCH 04/14] staging: ath6kl: check return code of get_user Dan Carpenter
2010-09-16 13:23       ` [PATCH 04/14] staging: ath6kl: check return code of get_user and put_user Dan Carpenter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100916125908.GA4491@albatros \
    --to=segooon@gmail.com \
    --cc=Vipin.Mehta@Atheros.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.