| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200903251642.40442.arnd@arndb.de> Date: Wed, 25 Mar 2009 16:42:40 +0100 From: Arnd Bergmann <arnd@...db.de> To: monstr@...str.eu Cc: linux-kernel@...r.kernel.org, john.williams@...alogix.com Subject: Re: [PATCH 01/57] microblaze_v7: Kconfig patches On Wednesday 18 March 2009, monstr@...str.eu wrote: > From: Michal Simek <monstr@...str.eu> > > > Signed-off-by: Michal Simek <monstr@...str.eu> > --- > arch/microblaze/Kconfig | 136 +++++++++++++++++++++++++ > arch/microblaze/Kconfig.debug | 26 +++++ > arch/microblaze/platform/Kconfig.platform | 85 +++++++++++++++ > arch/microblaze/platform/generic/Kconfig.auto | 62 +++++++++++ > 4 files changed, 309 insertions(+), 0 deletions(-) > create mode 100644 arch/microblaze/Kconfig > create mode 100644 arch/microblaze/Kconfig.debug > create mode 100644 arch/microblaze/platform/Kconfig.platform > create mode 100644 arch/microblaze/platform/generic/Kconfig.auto As a general rule for future updates, you should make sure that the order of your patches is so that you don't get a broken version in the middle. In your current series, it's not important, because nothing works really until all your patches are in there. Arnd <>< -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists