From: Andrew Victor <andrew@sanpeople.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, Russell King <rmk@arm.linux.org.uk>
Subject: Re: [RFC] Atmel-supplied hardware headers for AT91RM9200 SoC processor
Date: 08 Jul 2005 09:10:44 +0200 [thread overview]
Message-ID: <1120806643.24896.26.camel@fuzzie.sanpeople.com> (raw)
In-Reply-To: <200507080152.03976.adobriyan@gmail.com>
hi Alexey,
Thanks for the constructive comments.
> And check for non-NULL data in at91_add_device_usbh() is useless:
There are many more custom AT91RM9200-based boards. That NULL check is
really just there to help the developers when they write their own
board-XX.c file.
> at91_wdt_ioctl() isn't __user annotated. Let alone it is ioctl.
All the other watchdog drivers use ioctl? That is how it's described in
Documentation/watchdog/watchdog-api.txt.
> > + char* command = kmalloc(2, GFP_KERNEL);
>
> Anyone remembers 1 kmallocated byte?
That command buffer is passed down to the SPI driver, which then DMA's
directly from/to it. We can't DMA to an address on the stack (atleast
not in 2.4 when that driver was written).
Regards,
Andrew Victor
next prev parent reply other threads:[~2005-07-08 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 9:58 Andrew Victor
2005-07-07 13:06 ` Christoph Hellwig
2005-07-11 13:35 ` Alan Cox
2005-07-11 13:57 ` Andrew Victor
2005-07-11 15:20 ` Alan Cox
2005-07-11 15:48 ` Christoph Hellwig
2005-07-07 14:41 ` David Woodhouse
2005-07-07 15:14 ` Andrew Victor
2005-07-07 15:26 ` David Woodhouse
2005-07-07 21:52 ` Alexey Dobriyan
2005-07-08 7:10 ` Andrew Victor [this message]
2005-07-08 14:50 ` Ben Dooks
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=1120806643.24896.26.camel@fuzzie.sanpeople.com \
--to=andrew@sanpeople.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®