Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: [PATCH 00/17] drop unused Kconfig symbols
2 views
Skip to first unread message
Michal Marek
Oct 31, 2011, 6:50:02 PM10/31/11
to
On Mon, Oct 24, 2011 at 01:37:35PM +0200, Paul Bolle wrote:
> 0) This is what's left of the Kconfig patches that I send (to
> maintainers and lkml) ten days ago.
>
> 1) I've dropped five patches that were taken by the maintainers
> (blackfin, unicore32, tomoyo, m68k, and staging). cris got a NAK (for an
> invalid reason, but I guess I'll just try again after the v3.2 merge
> window closes).
>
> 2) I've added all the tags the rest of these patches collected.
>
> 3) No further tests were done since I first send these (not that the
> tests done then were very thorough).
>
> 4) I'll send these patches only to you and the people that added a tag.
> Please tell me if you'd like me to also cc lkml and the maintainers. I
> assumed cc'ing those addresses would not be helpful in this stage.
>
> Paul Bolle (17):
> alpha: drop unused Kconfig symbol
> sparc: drop unused Kconfig symbol
> um: drop unused Kconfig symbol
> sh: drop unused Kconfig symbol
> score: drop unused Kconfig symbols
> m32r: drop unused Kconfig symbol
> samples: drop unused Kconfig symbol
> arm: at91: drop unused Kconfig symbol
> (arm: drop unused Kconfig symbol -- skipped)
> openrisc: drop unused Kconfig symbols
> mips: drop unused Kconfig symbols
> powerpc: 40x: drop unused Kconfig symbol
> powerpc: drop unused Kconfig symbols
> x86: drop unused Kconfig symbol
> stmmac: drop unused Kconfig symbol
> pci: drop unused Kconfig symbol
> scsi: drop unused Kconfig symbol
Applied except for the one arm commit.
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> 0) This is what's left of the Kconfig patches that I send (to
> maintainers and lkml) ten days ago.
>
> 1) I've dropped five patches that were taken by the maintainers
> (blackfin, unicore32, tomoyo, m68k, and staging). cris got a NAK (for an
> invalid reason, but I guess I'll just try again after the v3.2 merge
> window closes).
>
> 2) I've added all the tags the rest of these patches collected.
>
> 3) No further tests were done since I first send these (not that the
> tests done then were very thorough).
>
> 4) I'll send these patches only to you and the people that added a tag.
> Please tell me if you'd like me to also cc lkml and the maintainers. I
> assumed cc'ing those addresses would not be helpful in this stage.
>
> Paul Bolle (17):
> alpha: drop unused Kconfig symbol
> sparc: drop unused Kconfig symbol
> um: drop unused Kconfig symbol
> sh: drop unused Kconfig symbol
> score: drop unused Kconfig symbols
> m32r: drop unused Kconfig symbol
> samples: drop unused Kconfig symbol
> arm: at91: drop unused Kconfig symbol
> (arm: drop unused Kconfig symbol -- skipped)
> openrisc: drop unused Kconfig symbols
> mips: drop unused Kconfig symbols
> powerpc: 40x: drop unused Kconfig symbol
> powerpc: drop unused Kconfig symbols
> x86: drop unused Kconfig symbol
> stmmac: drop unused Kconfig symbol
> pci: drop unused Kconfig symbol
> scsi: drop unused Kconfig symbol
Applied except for the one arm commit.
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Paul Bolle
Oct 31, 2011, 7:00:02 PM10/31/11
to
On Mon, 2011-10-31 at 23:42 +0100, Michal Marek wrote:
> On Mon, Oct 24, 2011 at 01:37:35PM +0200, Paul Bolle wrote:
> > 1) I've dropped five patches that were taken by the maintainers
> > (blackfin, unicore32, tomoyo, m68k, and staging). cris got a NAK (for an
> > invalid reason, but I guess I'll just try again after the v3.2 merge
> > window closes).
Just today Jesper Nilsson basically dropped that NAK. I assume Jesper
> On Mon, Oct 24, 2011 at 01:37:35PM +0200, Paul Bolle wrote:
> > 1) I've dropped five patches that were taken by the maintainers
> > (blackfin, unicore32, tomoyo, m68k, and staging). cris got a NAK (for an
> > invalid reason, but I guess I'll just try again after the v3.2 merge
> > window closes).
will try to carry the patch in (one of) their tree(s). Is that correct?
> > 4) I'll send these patches only to you and the people that added a tag.
> > Please tell me if you'd like me to also cc lkml and the maintainers. I
> > assumed cc'ing those addresses would not be helpful in this stage.
> >
> > Paul Bolle (17):
> > alpha: drop unused Kconfig symbol
> > sparc: drop unused Kconfig symbol
> > um: drop unused Kconfig symbol
> > sh: drop unused Kconfig symbol
handle that somewhere down the road.
> > score: drop unused Kconfig symbols
> > m32r: drop unused Kconfig symbol
> > samples: drop unused Kconfig symbol
> > arm: at91: drop unused Kconfig symbol
> > (arm: drop unused Kconfig symbol -- skipped)
> > openrisc: drop unused Kconfig symbols
> > mips: drop unused Kconfig symbols
> > powerpc: 40x: drop unused Kconfig symbol
> > powerpc: drop unused Kconfig symbols
> > x86: drop unused Kconfig symbol
> > stmmac: drop unused Kconfig symbol
> > pci: drop unused Kconfig symbol
> > scsi: drop unused Kconfig symbol
>
> Applied except for the one arm commit.
Jesper Nilsson
Nov 1, 2011, 5:00:02 AM11/1/11
to
On Mon, Oct 31, 2011 at 11:55:16PM +0100, Paul Bolle wrote:
> On Mon, 2011-10-31 at 23:42 +0100, Michal Marek wrote:
> > On Mon, Oct 24, 2011 at 01:37:35PM +0200, Paul Bolle wrote:
> > > 1) I've dropped five patches that were taken by the maintainers
> > > (blackfin, unicore32, tomoyo, m68k, and staging). cris got a NAK (for an
> > > invalid reason, but I guess I'll just try again after the v3.2 merge
> > > window closes).
>
> 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.
> On Mon, 2011-10-31 at 23:42 +0100, Michal Marek wrote:
> > On Mon, Oct 24, 2011 at 01:37:35PM +0200, Paul Bolle wrote:
> > > 1) I've dropped five patches that were taken by the maintainers
> > > (blackfin, unicore32, tomoyo, m68k, and staging). cris got a NAK (for an
> > > invalid reason, but I guess I'll just try again after the v3.2 merge
> > > window closes).
>
> 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?
> Paul Bolle
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper....@axis.com
Paul Bolle
Nov 1, 2011, 5:50:01 AM11/1/11
to
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 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.
On Fri, Oct 14, 2011 at 09:11:01PM +0200, Valdis.K...@vt.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.
Paul Bolle
Jesper Nilsson
Nov 1, 2011, 6:20:01 AM11/1/11
to
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.K...@vt.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.
> 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.K...@vt.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.
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
Nov 1, 2011, 6:40:01 AM11/1/11
to
On Tue, 2011-11-01 at 11:12 +0100, Jesper Nilsson wrote:
> 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?
I can't really complain if you decide to carry a patch I submitted, can
> 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?
I? So, yes, this is OK with me.
Thanks for clearing this up.
Paul Bolle
0 new messages