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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 03 Jun 2016 10:58:15 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	Gerd Hoffmann <kraxel@...hat.com>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	open list <linux-kernel@...r.kernel.org>,
	Eric Anholt <eric@...olt.net>,
	linux-rpi-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 5/9] arm64: Add BCM2835 support to the defconfig.

On Friday, June 3, 2016 10:50:16 AM CEST Gerd Hoffmann wrote:
> On Fr, 2016-06-03 at 09:36 +0200, Arnd Bergmann wrote:
> > On Friday, June 3, 2016 8:18:24 AM CEST Gerd Hoffmann wrote:
> > > From: Eric Anholt <eric@...olt.net>
> > > 
> > > Made with make defconfig; make menuconfig (only saying Y to new
> > > entries); make savedefconfig.
> > 
> > Please try not to mix 'make savedefconfig' changes with your
> > own changes, it make it harder to review and can lead to more
> > conflicts.
> 
> This is just conflicts resolved by hand after 4.6 -> 4.7-rc1 rebase,
> latest version didn't actually ran through savedefconfig.  Probably some
> unwanted changes made it in by accident this way.
> 
> Guess I better redo this from scratch.
> 
> What is the suggested procedure to generate defconfig patches?

I tend to just edit the files by hand, or use 'make savedefconfig' to
create an initial version, and then use 'vimdiff' to revert the changes
I don't want.

	Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ