From: David Howells <dhowells@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: dhowells@redhat.com, Jiri Kosina <trivial@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Trivial PATCH 02/33] frv: Convert use of typedef ctl_table to struct ctl_table
Date: Fri, 14 Jun 2013 09:57:43 +0100 [thread overview]
Message-ID: <7254.1371200263@warthog.procyon.org.uk> (raw)
In-Reply-To: <9fc3b9d2c9dd12c74aab5115a3c50b9eb3ae76d5.1371177118.git.joe@perches.com>
These look okay. Feel free to add my Acked-by. I presume they can't become
const also?
David
prev parent reply other threads:[~2013-06-14 8:57 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 2:37 [Trivial PATCH 00/33] Remove uses of typedef ctl_table Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 01/33] arm: kernel: isa: Convert use of typedef ctl_table to struct ctl_table Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 02/33] frv: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 03/33] ia64: crash: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 04/33] mips: lasat: sysctl: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 05/33] powerpc: idle: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 06/33] s390: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 07/33] tile: proc: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 08/33] x86: vdso: " Joe Perches
2013-06-19 18:43 ` [tip:x86/asm] x86/vdso: " tip-bot for Joe Perches
2013-06-19 18:47 ` H. Peter Anvin
2013-06-19 19:05 ` Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 09/33] cdrom: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 10/33] char: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 11/33] infiniband: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 12/33] macintosh: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 13/33] md: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 14/33] sgi: xpc: " Joe Perches
2013-06-14 2:53 ` Robin Holt
2013-06-14 2:37 ` [Trivial PATCH 15/33] parport: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 16/33] scsi_sysctl: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 17/33] coda: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 18/33] fscache: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 19/33] lockd: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 20/33] nfs: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 21/33] inotify: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 22/33] ntfs: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 23/33] ocfs2: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 24/33] quota: " Joe Perches
2013-06-21 12:59 ` Jan Kara
2013-06-14 2:37 ` [Trivial PATCH 25/33] xfs: " Joe Perches
2013-06-14 5:21 ` Dave Chinner
2013-06-14 5:33 ` Joe Perches
2013-06-14 6:18 ` Dave Chinner
2013-06-17 22:39 ` Ben Myers
2013-06-14 2:37 ` [Trivial PATCH 26/33] fs: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 27/33] key: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 28/33] ipv6: " Joe Perches
2013-06-20 6:18 ` David Miller
2013-06-14 2:37 ` [Trivial PATCH 29/33] ndisc: " Joe Perches
2013-06-20 6:18 ` David Miller
2013-06-14 2:37 ` [Trivial PATCH 30/33] ipc: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 31/33] sysctl: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 32/33] mm: " Joe Perches
2013-06-14 2:37 ` [Trivial PATCH 33/33] security: keys: " Joe Perches
2013-06-14 8:57 ` David Howells [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=7254.1371200263@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome