Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
On Tue, 06 Nov 2007 13:12:23 -0800 H. Peter Anvin wrote:
> Ideally architecture should be a Kconfig option (it's not needed before
> config runs, unlike, say HOSTCC.)
>
> That might take some major surgery, though.
I think that's what Sam was going to try to get to.
He said that we need all
Ideally architecture should be a Kconfig option (it's not needed before
config runs, unlike, say HOSTCC.)
That might take some major surgery, though.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
On Tue, 06 Nov 2007 13:12:23 -0800 H. Peter Anvin wrote:
Ideally architecture should be a Kconfig option (it's not needed before
config runs, unlike, say HOSTCC.)
That might take some major surgery, though.
I think that's what Sam was going to try to get to.
He said that we need all ARCHes
Ideally architecture should be a Kconfig option (it's not needed before
config runs, unlike, say HOSTCC.)
That might take some major surgery, though.
-hpa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the "General setup" menu.
Linus:
> Should it come with a re-duplication of it's content into each
> architecture, which was the case previously ? The oprofile and kprobes
> menu entries were litteraly cut and pasted from one architecture to
> another. Should
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
Puts the content of arch/Kconfig in the General setup menu.
Linus:
Should it come with a re-duplication of it's content into each
architecture, which was the case previously ? The oprofile and kprobes
menu entries were litteraly cut and pasted from one architecture to
another. Should we put
22 matches
Mail list logo
