linux-kernel - Re: [PATCH 00/17] drop unused Kconfig symbols

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:	Tue, 1 Nov 2011 11:12:27 +0100
From:	Jesper Nilsson <jesper.nilsson@...s.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Michal Marek <mmarek@...e.cz>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Mikael Starvik <starvik@...s.com>,
	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>
Subject: Re: [PATCH 00/17] drop unused Kconfig symbols

On Tue, Nov 01, 2011 at 10:46:04AM +0100, Paul Bolle wrote:
> On Tue, 2011-11-01 at 09:59 +0100, Jesper Nilsson wrote:
> > On Mon, Oct 31, 2011 at 11:55:16PM +0100, Paul Bolle wrote:
> > > Just today Jesper Nilsson basically dropped that NAK. I assume Jesper
> > > will try to carry the patch in (one of) their tree(s). Is that correct?
> > 
> > The patch that reintroduces the Kconfigs, yes, the one that removes them, no.
> 
> But yesterday you wrote:
> On Fri, Oct 14, 2011 at 09:11:01PM +0200, Valdis.Kletnieks@...edu wrote:
> [...]
> > > (Personally, I'm tending towards unless it's going to be in linux-next within
> > > the next month or so, pull the Kconfig variables out and the driver can re-add
> > > them when it actually lands)
> > 
> > Ok, let's do it the right way and remove them now, and I can re-add
> > them in the same tree.
> 
> So your plans have changed? It's OK with me if they change, of course,
> but now I'm unsure what you intend to do.

Sorry, I was unclear and not complete in my sentence above.
I was referring above to the tree that the drivers will be added in,
not the one where the Kconfigs will be removed.

I assumed that the removal patch was handled elsewhere, so I didn't
pick up the original patch which removed them.

So, just to be clear on what I intend to do (now that I know what you meant):

- Pick up the removal patch to the CRIS-tree.
- Create a new tree/branch with the missing drivers and the Kconfigs readded.

Does this seem allright for you?

> Paul Bolle

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@...s.com
--
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/