linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johnny Kim <johnny.kim@atmel.com>
To: Greg KH <gregkh@linuxfoundation.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Rachel Kim <rachel.kim@atmel.com>, Dean Lee <dean.lee@atmel.com>,
	"Chris Park" <chris.park@atmel.com>, <devel@driverdev.osuosl.org>,
	<nicolas.ferre@atmel.com>, <linux-kernel@vger.kernel.org>,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: Re: [PATCH v3 00/12] wilc1000: dead code removal and other cleanup
Date: Tue, 2 Jun 2015 15:23:20 +0900	[thread overview]
Message-ID: <556D4BD8.20204@atmel.com> (raw)
In-Reply-To: <20150602052023.GA21903@kroah.com>


On 2015년 06월 02일 14:20, Greg KH wrote:
> On Tue, Jun 02, 2015 at 01:53:31PM +0900, Greg KH wrote:
>> On Mon, Jun 01, 2015 at 09:06:33PM +0200, Arnd Bergmann wrote:
>>> Hi Greg,
>>>
>>> Next try, I've rebased on top of your staging-testing branch
>>> and fixed the two build errors.
>>>
>>> While I had done my normal build testing on the driver (a few
>>> hundred randconfig builds), I don't normally do 'make clean',
>>> so the stale Makefile entry ended up picking the old object
>>> files and succeeding with that.
>> Thanks, I've applied these but there are still a bunch of warnings.
>> It's obvious no one has ever built this code on a 64bit processor
>> (Atmel, come on, not all the world is 32bits...)
>>
>> I'll take a pass at it to see if I can clean up some stuff to maybe
>> reduce the number of warnings, but right now, it's still way too many
>> for linux-next to want to enable as it blows up their logs...
> Ugh, that's a rabbit hole you can disappear into for a long time.  I did
> a few patches but ran out of time, I can spend days mucking down in
> there unwinding the mess...
>
> Johnny, Rachel, Dean, and Chris, can you all fix up all of the build
> warnings as soon as possible?  Take my tree and work off of that, just
> build it on your desktop 64bit Linux build and get rid of all of them
> properly and send me the patches.  Hopefully by the end of this week so
> that linux-next can get some testing with this driver enabled.

OK. I will fix the warnings and 64bits dependency on current 
staging-next by the end of this week.
Thanks for your review.

Best regards.
Johnny.

      reply	other threads:[~2015-06-02  6:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 19:06 [PATCH v3 00/12] wilc1000: dead code removal and other cleanup Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 01/12] staging: wilc1000: remove time wrapper Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 02/12] staging: wilc1000: remove unused string functions Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 03/12] staging: wilc1000: simplify msgqueue code Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 04/12] staging: wilc1000: remove unused memory handling code Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 05/12] staging: wilc1000: simplify semaphore wrapper Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 06/12] staging: wilc1000: clean up sleep wrapper Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 07/12] staging: wilc1000: clean up timer feature Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 08/12] staging: wilc1000: remove unused OS abstraction features Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 09/12] staging: wilc1000: remove EXPORT_SYMTAB Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 10/12] staging: wilc1000: remove semaphore wrapper Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 11/12] staging: wilc1000: fix const cast warnings Arnd Bergmann
2015-06-01 19:06 ` [PATCH v2 12/12] staging: wilc1000: fix compiler warnings Arnd Bergmann
2015-06-02  4:53 ` [PATCH v3 00/12] wilc1000: dead code removal and other cleanup Greg KH
2015-06-02  5:20   ` Greg KH
2015-06-02  6:23     ` Johnny Kim [this message]

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=556D4BD8.20204@atmel.com \
    --to=johnny.kim@atmel.com \
    --cc=arnd@arndb.de \
    --cc=chris.park@atmel.com \
    --cc=dean.lee@atmel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=rachel.kim@atmel.com \
    --cc=sudipm.mukherjee@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).