From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc2-mm1
Date: Thu, 9 Aug 2007 22:30:33 +0200 [thread overview]
Message-ID: <9a8748490708091330u687f2ca8sc85b7696be420973@mail.gmail.com> (raw)
In-Reply-To: <20070809015106.cd0bfc53.akpm@linux-foundation.org>
On 09/08/07, Andrew Morton <akpm@linux-foundation.org> wrote:
...
> - If there's a patch in here which you think should be in 2.6.23 but I do
> not have it designated in that way, please be sure to let me know.
...
Well, if you want to clean up your patch queue a bit then I have a few
suggestions for some patches of mine that are currently in -mm that
you could push to Linus. They are not really important, so if you'd
rather keep them around in -mm until the next merge window then that's
fine by me, but they should be safe to push and would get cut down on
the number of patches you track a bit :-)
This fix was already merged for the ati side of things, this is an
identical fix for the amd side of things - I see no reason why we
shouldn't get this fix into 2.6.23 as well :
fix-use-after-free--double-free-bug-in-amd_create_gatt_pages--amd_free_gatt_pages.patch
This patch only changes the output of the script when run without
arguments, so as far as building the kernel goes it can't cause any
regressions and it's a clear improvement over what we currently have,
so might as well get it out of your queue and upstream :
improve-scripts-gcc-versionsh-output-a-bit-when-called-without-args.patch
When people use scripts/ver_linux in bugreports we want correct info -
currently we often print wrong info for the binutils version. This
patch doesn't hurt existing working scenarios but does fix a few
broken ones, might as well get that merged, it's a clear fix :
scripts-ver_linux-correct-printing-of-binutils-version.patch
These should all be trivially correct since they just remove duplicate
#include's of the same header into a .c file outside any #ifdef and
similar magic, so they should be quite safe to push. Also, I haven't
seen anything but ACK's in response to them (when I've seen a
response), and a few of my similar patches have already been merged :
powerpc-clean-out-a-bunch-of-duplicate-includes.patch
clean-up-duplicate-includes-in-drivers-input.patch
clean-up-duplicate-includes-in-drivers-net.patch
clean-up-duplicate-includes-in-drivers-atm.patch
clean-up-duplicate-includes-in-net-atm.patch
clean-up-duplicate-includes-in-net-ipv4.patch
clean-up-duplicate-includes-in-net-ipv6.patch
clean-up-duplicate-includes-in-net-sched.patch
clean-up-duplicate-includes-in-net-sunrpc.patch
clean-up-duplicate-includes-in-net-tipc.patch
clean-up-duplicate-includes-in-net-xfrm.patch
clean-up-duplicate-includes-in-include-linux-nfs_fsh.patch
clean-up-duplicate-includes-in-fs-ntfs.patch
clean-up-duplicate-includes-in-drivers-scsi.patch
clean-up-duplicate-includes-in-drivers-block.patch
clean-up-duplicate-includes-in-arch-i386-xen.patch
clean-up-duplicate-includes-in-include-linux-memory_hotplugh.patch
clean-up-duplicate-includes-in-mm.patch
clean-up-duplicate-includes-in-drivers-char.patch
clean-up-duplicate-includes-in-drivers-w1.patch
clean-up-duplicate-includes-in-fs.patch
clean-up-duplicate-includes-in-fs-ecryptfs.patch
clean-up-duplicate-includes-in-kernel.patch
clean-up-duplicate-includes-in-drivers-spi.patch
clean-up-duplicate-includes-in-documentation.patch
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2007-08-09 20:30 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 8:51 2.6.23-rc2-mm1 Andrew Morton
2007-08-09 10:10 ` [usb-storage] schedule_timeout: wrong timeout value c1a95554 Mariusz Kozlowski
2007-08-09 14:43 ` [linux-usb-devel] " Alan Stern
2007-08-09 15:07 ` Rafael J. Wysocki
2007-08-09 15:20 ` Mariusz Kozlowski
2007-08-09 19:15 ` Rafael J. Wysocki
2007-08-09 12:53 ` 2.6.23-rc2-mm1 -- spinlock bad magic Andy Whitcroft
2007-08-09 17:17 ` Andy Whitcroft
2007-08-09 13:04 ` 2.6.23-rc2-mm1 -- PPC G5 kernel compile failure Andy Whitcroft
2007-08-09 14:20 ` 2.6.23-rc2-mm1 -- PPC G5 kernel compile failure (patch) Krzysztof Helt
2007-08-09 17:18 ` Andy Whitcroft
2007-08-10 13:09 ` Andy Whitcroft
2007-08-09 13:23 ` 2.6.23-rc2-mm1 Michal Piotrowski
2007-08-09 18:37 ` 2.6.23-rc2-mm1 Andrew Morton
2007-08-09 19:04 ` 2.6.23-rc2-mm1 Michal Piotrowski
2007-08-09 19:10 ` 2.6.23-rc2-mm1 Andrew Morton
2007-08-09 19:27 ` 2.6.23-rc2-mm1 Jeff Garzik
2007-08-09 13:51 ` 2.6.23-rc2-mm1: e1000e global symbols must be renamed Adrian Bunk
2007-08-09 17:06 ` [E1000-devel] " Kok, Auke
2007-08-09 14:24 ` 2.6.23-rc2-mm1: no bcm43xx Rafael J. Wysocki
2007-08-09 14:16 ` Michael Buesch
2007-08-09 15:11 ` 2.6.23-rc2-mm1: kernel BUG at mm/swap_state.c:78! Mariusz Kozlowski
2007-08-09 15:14 ` Adrian Bunk
2007-08-09 15:25 ` Mariusz Kozlowski
2007-08-09 15:37 ` Hugh Dickins
2007-08-09 16:00 ` Michal Piotrowski
2007-08-10 0:30 ` Nick Piggin
2007-08-09 15:36 ` 2.6.23-rc2-mm1 Michal Piotrowski
2007-08-09 16:19 ` 2.6.23-rc2-mm1 Michal Piotrowski
2007-08-09 17:04 ` 2.6.23-rc2-mm1 Andrew Morton
2007-08-09 16:31 ` 2.6.23-rc2-mm1 Andrew Morton
2007-08-09 20:17 ` 2.6.23-rc2-mm1: silly df numbers on 32bit extN Hugh Dickins
2007-08-09 20:56 ` Andrew Morton
2007-08-09 20:30 ` Jesper Juhl [this message]
2007-08-09 21:36 ` 2.6.23-rc2-mm1 Gabriel C
2007-08-09 22:04 ` 2.6.23-rc2-mm1 Andrew Morton
2007-08-09 22:42 ` 2.6.23-rc2-mm1 Alan Cox
2007-08-09 23:33 ` 2.6.23-rc2-mm1 Gabriel C
2007-08-09 23:23 ` 2.6.23-rc2-mm1: sleeping function called from invalid context at kernel/mutex.c:86 Mariusz Kozlowski
2007-08-10 0:11 ` Andrew Morton
2007-08-10 5:36 ` Josh Triplett
2007-08-10 7:27 ` Mariusz Kozlowski
2007-08-10 7:40 ` Ingo Molnar
2007-08-10 7:55 ` Andrew Morton
2007-08-11 7:24 ` Alexey Dobriyan
2007-08-09 23:49 ` 2.6.23-rc2-mm1: rtl8139 inconsistent lock state Mariusz Kozlowski
2007-08-22 13:35 ` [PATCH 2.6.23-rc3-mm1] request_irq fix DEBUG_SHIRQ handling " Jarek Poplawski
2007-08-25 9:43 ` Mariusz Kozlowski
2007-08-27 5:54 ` Jarek Poplawski
2007-08-23 8:44 ` [PATCH (take 2)] " Jarek Poplawski
2007-08-24 5:46 ` Jarek Poplawski
2007-08-10 1:31 ` 2.6.23-rc2-mm1: rcutorture xtime usage Adrian Bunk
2007-08-10 2:00 ` Paul E. McKenney
2007-08-10 2:06 ` Andrew Morton
2007-08-10 15:12 ` Paul E. McKenney
2007-08-10 17:12 ` Andrew Morton
2007-08-10 20:30 ` Paul E. McKenney
2007-08-11 0:29 ` Paul E. McKenney
2007-08-11 4:47 ` Paul E. McKenney
2007-08-11 18:09 ` Ingo Molnar
2007-08-11 19:39 ` Paul E. McKenney
2007-08-10 2:22 ` Adrian Bunk
2007-08-10 7:06 ` 2.6.23-rc2-mm1: irq lock inversion dependency detected Mariusz Kozlowski
2007-08-24 8:27 ` Jarek Poplawski
2007-08-24 8:50 ` Jarek Poplawski
2007-08-14 21:22 ` [-mm patch] make fs/nfsd/nfs4callback.c:do_probe_callback() static Adrian Bunk
2007-08-14 22:02 ` J. Bruce Fields
2007-08-14 21:23 ` [-mm patch] make drivers/ata/libata-scsi.c:ata_scsi_link_pm_policy() static Adrian Bunk
2007-08-14 21:23 ` [-mm patch] unexport ide_acpi_set_state Adrian Bunk
2007-08-14 21:23 ` [-mm patch] drivers/mtd/mtdbdi.c is no longer an own module Adrian Bunk
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=9a8748490708091330u687f2ca8sc85b7696be420973@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=akpm@linux-foundation.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 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®