Re: [GIT PULL] S+core Architecture : fix bugs for compiling and support necessary functions
Hi Guenter, What does the "e-mail is not signed" mean? I try to search some information, but I still do not understand what you say. Best, Lennox 2013/9/16 Lennox Wu : > OK, thanks for your reminding, most the format is referenced from > other git pull requests, however, I still miss something, I will fix > them. > > How detailed content shold a summary have? I indeed have made some > summary in the commits. Could you give me an example? > > About why I didn't send a copy to Linus. Because the document > SubmittingPatches has no this rule. I indeed notice that many git > pull requests sent a copy to Linus, but I think I should follow the > documented rule. If it is a new rule, thanks for telling me the rule > ,and maybe the document should be added this rule. > Adopt this rule... > " > 5) Select e-mail destination. > Look through the MAINTAINERS file and the source code, and determine > if your change applies to a specific subsystem of the kernel, with > an assigned maintainer. If so, e-mail that person. The script > scripts/get_maintainer.pl can be very useful at this step. > If no maintainer is listed, or the maintainer does not respond, send > your patch to the primary Linux kernel developer's mailing list, > linux-kernel@vger.kernel.org. Most kernel developers monitor this > e-mail list, and can comment on your changes. > > Do not send more than 15 patches at once to the vger mailing lists!!! > > Linus Torvalds is the final arbiter of all changes accepted into the > Linux kernel. His e-mail address is . > He gets a lot of e-mail, so typically you should do your best to -avoid- > sending him e-mail. > " > > Anyway, I appreciate your notifiction and I will fix this errors. > > Best, > Lennox > > > 2013/9/16 Guenter Roeck : >> On Sat, Sep 14, 2013 at 05:42:07PM +0800, Lennox Wu wrote: >>> Hi Linus, >>> Please pull these updates for S+core architecture. These updates include >>> updating information of maintainers, fix some trivial errors, and add >>> a necessary function for supporting ipv6. >>> >>> The following changes since commit bdbdfdef5766c2a60185e946df242f1bc0d37c09 >>> >>> Merge tag 'hwmon-for-linus' of >>> git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging >>> (Fri Sep 13 10:58:41 2013 -0700) >>> >>> on >>> >>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git >>> >>> >>> For you to fetch changes up to 969f99168b9dff2f6cc07cdf14255178d4397c4f >>> >>> g...@github.com:sctscore/official-linux.git tags/branch-linus-20130914 >>> >>> Best, >>> Lennox Wu >>> >> Your e-mail is not signed. You don't even have a pgp key as far as >> I can see, at least not one associated with your e-mail address. >> How do you expect anyone to establish your identity ? >> >> In addition to that, the tag in your repository is not signed and >> does not contain a summary of your changes. Your patches do not >> have a Signed-off-by: tag. The pull message below appears to be >> hand-edited and does not match an auto-generated pull request >> (which should have given you a hint that the commit logs have >> a problem). >> >> You did not even copy Linus on this e-mail. Do you really think >> he would even notice your pull request, much less apply it ? >> >> Guenter >> >>> --- >>> Summary these commits: >>> 1. Fix some trivial errors for successfully compiling the latest >>> version Linux kernel. >>> 2. Provide necessary function for support IPV6. >>> 3. Update the information of maintainers. >>> >>> Lennox Wu (8): >>> score : Update the information of Score maintainers >>> score : Implement the function csum_ipv6_magic >>> score : arch/score/kernel/entry.S: fix wrong instructions >>> score : arch/score/kernel/process.c : fix some typos >>> score : Modify the MAKEFILE of Score >>> >>> MAINTAINERS |4 +- >>> arch/score/Kconfig|4 ++ >>> arch/score/Makefile |4 +- >>> arch/score/include/asm/checksum.h | 93 >>> - >>> arch/score/include/asm/io.h |1 - >>> arch/score/include/asm/pgalloc.h |2 +- >>> arch/score/kernel/entry.S |4 +- >>> arch/score/kernel/process.c |4 +- >>> 8 files changed, 64 insertions(+), 52 deletions(-) >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >>> the body of a message to majord...@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> Please read the FAQ at http://www.tux.org/lkml/ >>> >>> >>> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [GIT PULL] S+core Architecture : fix bugs for compiling and support necessary functions
Hi Guenter, What does the e-mail is not signed mean? I try to search some information, but I still do not understand what you say. Best, Lennox 2013/9/16 Lennox Wu lennox...@gmail.com: OK, thanks for your reminding, most the format is referenced from other git pull requests, however, I still miss something, I will fix them. How detailed content shold a summary have? I indeed have made some summary in the commits. Could you give me an example? About why I didn't send a copy to Linus. Because the document SubmittingPatches has no this rule. I indeed notice that many git pull requests sent a copy to Linus, but I think I should follow the documented rule. If it is a new rule, thanks for telling me the rule ,and maybe the document should be added this rule. Adopt this rule... 5) Select e-mail destination. Look through the MAINTAINERS file and the source code, and determine if your change applies to a specific subsystem of the kernel, with an assigned maintainer. If so, e-mail that person. The script scripts/get_maintainer.pl can be very useful at this step. If no maintainer is listed, or the maintainer does not respond, send your patch to the primary Linux kernel developer's mailing list, linux-kernel@vger.kernel.org. Most kernel developers monitor this e-mail list, and can comment on your changes. Do not send more than 15 patches at once to the vger mailing lists!!! Linus Torvalds is the final arbiter of all changes accepted into the Linux kernel. His e-mail address is torva...@linux-foundation.org. He gets a lot of e-mail, so typically you should do your best to -avoid- sending him e-mail. Anyway, I appreciate your notifiction and I will fix this errors. Best, Lennox 2013/9/16 Guenter Roeck li...@roeck-us.net: On Sat, Sep 14, 2013 at 05:42:07PM +0800, Lennox Wu wrote: Hi Linus, Please pull these updates for S+core architecture. These updates include updating information of maintainers, fix some trivial errors, and add a necessary function for supporting ipv6. The following changes since commit bdbdfdef5766c2a60185e946df242f1bc0d37c09 Merge tag 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (Fri Sep 13 10:58:41 2013 -0700) on git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git For you to fetch changes up to 969f99168b9dff2f6cc07cdf14255178d4397c4f g...@github.com:sctscore/official-linux.git tags/branch-linus-20130914 Best, Lennox Wu Your e-mail is not signed. You don't even have a pgp key as far as I can see, at least not one associated with your e-mail address. How do you expect anyone to establish your identity ? In addition to that, the tag in your repository is not signed and does not contain a summary of your changes. Your patches do not have a Signed-off-by: tag. The pull message below appears to be hand-edited and does not match an auto-generated pull request (which should have given you a hint that the commit logs have a problem). You did not even copy Linus on this e-mail. Do you really think he would even notice your pull request, much less apply it ? Guenter --- Summary these commits: 1. Fix some trivial errors for successfully compiling the latest version Linux kernel. 2. Provide necessary function for support IPV6. 3. Update the information of maintainers. Lennox Wu (8): score : Update the information of Score maintainers score : Implement the function csum_ipv6_magic score : arch/score/kernel/entry.S: fix wrong instructions score : arch/score/kernel/process.c : fix some typos score : Modify the MAKEFILE of Score MAINTAINERS |4 +- arch/score/Kconfig|4 ++ arch/score/Makefile |4 +- arch/score/include/asm/checksum.h | 93 - arch/score/include/asm/io.h |1 - arch/score/include/asm/pgalloc.h |2 +- arch/score/kernel/entry.S |4 +- arch/score/kernel/process.c |4 +- 8 files changed, 64 insertions(+), 52 deletions(-) -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [GIT PULL] S+core Architecture : fix bugs for compiling and support necessary functions
OK, thanks for your reminding, most the format is referenced from other git pull requests, however, I still miss something, I will fix them. How detailed content shold a summary have? I indeed have made some summary in the commits. Could you give me an example? About why I didn't send a copy to Linus. Because the document SubmittingPatches has no this rule. I indeed notice that many git pull requests sent a copy to Linus, but I think I should follow the documented rule. If it is a new rule, thanks for telling me the rule ,and maybe the document should be added this rule. Adopt this rule... " 5) Select e-mail destination. Look through the MAINTAINERS file and the source code, and determine if your change applies to a specific subsystem of the kernel, with an assigned maintainer. If so, e-mail that person. The script scripts/get_maintainer.pl can be very useful at this step. If no maintainer is listed, or the maintainer does not respond, send your patch to the primary Linux kernel developer's mailing list, linux-kernel@vger.kernel.org. Most kernel developers monitor this e-mail list, and can comment on your changes. Do not send more than 15 patches at once to the vger mailing lists!!! Linus Torvalds is the final arbiter of all changes accepted into the Linux kernel. His e-mail address is . He gets a lot of e-mail, so typically you should do your best to -avoid- sending him e-mail. " Anyway, I appreciate your notifiction and I will fix this errors. Best, Lennox 2013/9/16 Guenter Roeck : > On Sat, Sep 14, 2013 at 05:42:07PM +0800, Lennox Wu wrote: >> Hi Linus, >> Please pull these updates for S+core architecture. These updates include >> updating information of maintainers, fix some trivial errors, and add >> a necessary function for supporting ipv6. >> >> The following changes since commit bdbdfdef5766c2a60185e946df242f1bc0d37c09 >> >> Merge tag 'hwmon-for-linus' of >> git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging >> (Fri Sep 13 10:58:41 2013 -0700) >> >> on >> >> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git >> >> >> For you to fetch changes up to 969f99168b9dff2f6cc07cdf14255178d4397c4f >> >> g...@github.com:sctscore/official-linux.git tags/branch-linus-20130914 >> >> Best, >> Lennox Wu >> > Your e-mail is not signed. You don't even have a pgp key as far as > I can see, at least not one associated with your e-mail address. > How do you expect anyone to establish your identity ? > > In addition to that, the tag in your repository is not signed and > does not contain a summary of your changes. Your patches do not > have a Signed-off-by: tag. The pull message below appears to be > hand-edited and does not match an auto-generated pull request > (which should have given you a hint that the commit logs have > a problem). > > You did not even copy Linus on this e-mail. Do you really think > he would even notice your pull request, much less apply it ? > > Guenter > >> --- >> Summary these commits: >> 1. Fix some trivial errors for successfully compiling the latest >> version Linux kernel. >> 2. Provide necessary function for support IPV6. >> 3. Update the information of maintainers. >> >> Lennox Wu (8): >> score : Update the information of Score maintainers >> score : Implement the function csum_ipv6_magic >> score : arch/score/kernel/entry.S: fix wrong instructions >> score : arch/score/kernel/process.c : fix some typos >> score : Modify the MAKEFILE of Score >> >> MAINTAINERS |4 +- >> arch/score/Kconfig|4 ++ >> arch/score/Makefile |4 +- >> arch/score/include/asm/checksum.h | 93 >> - >> arch/score/include/asm/io.h |1 - >> arch/score/include/asm/pgalloc.h |2 +- >> arch/score/kernel/entry.S |4 +- >> arch/score/kernel/process.c |4 +- >> 8 files changed, 64 insertions(+), 52 deletions(-) >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >> the body of a message to majord...@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at http://www.tux.org/lkml/ >> >> >> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [GIT PULL] S+core Architecture : fix bugs for compiling and support necessary functions
OK, thanks for your reminding, most the format is referenced from other git pull requests, however, I still miss something, I will fix them. How detailed content shold a summary have? I indeed have made some summary in the commits. Could you give me an example? About why I didn't send a copy to Linus. Because the document SubmittingPatches has no this rule. I indeed notice that many git pull requests sent a copy to Linus, but I think I should follow the documented rule. If it is a new rule, thanks for telling me the rule ,and maybe the document should be added this rule. Adopt this rule... 5) Select e-mail destination. Look through the MAINTAINERS file and the source code, and determine if your change applies to a specific subsystem of the kernel, with an assigned maintainer. If so, e-mail that person. The script scripts/get_maintainer.pl can be very useful at this step. If no maintainer is listed, or the maintainer does not respond, send your patch to the primary Linux kernel developer's mailing list, linux-kernel@vger.kernel.org. Most kernel developers monitor this e-mail list, and can comment on your changes. Do not send more than 15 patches at once to the vger mailing lists!!! Linus Torvalds is the final arbiter of all changes accepted into the Linux kernel. His e-mail address is torva...@linux-foundation.org. He gets a lot of e-mail, so typically you should do your best to -avoid- sending him e-mail. Anyway, I appreciate your notifiction and I will fix this errors. Best, Lennox 2013/9/16 Guenter Roeck li...@roeck-us.net: On Sat, Sep 14, 2013 at 05:42:07PM +0800, Lennox Wu wrote: Hi Linus, Please pull these updates for S+core architecture. These updates include updating information of maintainers, fix some trivial errors, and add a necessary function for supporting ipv6. The following changes since commit bdbdfdef5766c2a60185e946df242f1bc0d37c09 Merge tag 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (Fri Sep 13 10:58:41 2013 -0700) on git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git For you to fetch changes up to 969f99168b9dff2f6cc07cdf14255178d4397c4f g...@github.com:sctscore/official-linux.git tags/branch-linus-20130914 Best, Lennox Wu Your e-mail is not signed. You don't even have a pgp key as far as I can see, at least not one associated with your e-mail address. How do you expect anyone to establish your identity ? In addition to that, the tag in your repository is not signed and does not contain a summary of your changes. Your patches do not have a Signed-off-by: tag. The pull message below appears to be hand-edited and does not match an auto-generated pull request (which should have given you a hint that the commit logs have a problem). You did not even copy Linus on this e-mail. Do you really think he would even notice your pull request, much less apply it ? Guenter --- Summary these commits: 1. Fix some trivial errors for successfully compiling the latest version Linux kernel. 2. Provide necessary function for support IPV6. 3. Update the information of maintainers. Lennox Wu (8): score : Update the information of Score maintainers score : Implement the function csum_ipv6_magic score : arch/score/kernel/entry.S: fix wrong instructions score : arch/score/kernel/process.c : fix some typos score : Modify the MAKEFILE of Score MAINTAINERS |4 +- arch/score/Kconfig|4 ++ arch/score/Makefile |4 +- arch/score/include/asm/checksum.h | 93 - arch/score/include/asm/io.h |1 - arch/score/include/asm/pgalloc.h |2 +- arch/score/kernel/entry.S |4 +- arch/score/kernel/process.c |4 +- 8 files changed, 64 insertions(+), 52 deletions(-) -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[GIT PULL] S+core Architecture : fix bugs for compiling and support necessary functions
Hi Linus, Please pull these updates for S+core architecture. These updates include updating information of maintainers, fix some trivial errors, and add a necessary function for supporting ipv6. The following changes since commit bdbdfdef5766c2a60185e946df242f1bc0d37c09 Merge tag 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (Fri Sep 13 10:58:41 2013 -0700) on git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git For you to fetch changes up to 969f99168b9dff2f6cc07cdf14255178d4397c4f g...@github.com:sctscore/official-linux.git tags/branch-linus-20130914 Best, Lennox Wu --- Summary these commits: 1. Fix some trivial errors for successfully compiling the latest version Linux kernel. 2. Provide necessary function for support IPV6. 3. Update the information of maintainers. Lennox Wu (8): score : Update the information of Score maintainers score : Implement the function csum_ipv6_magic score : arch/score/kernel/entry.S: fix wrong instructions score : arch/score/kernel/process.c : fix some typos score : Modify the MAKEFILE of Score MAINTAINERS |4 +- arch/score/Kconfig|4 ++ arch/score/Makefile |4 +- arch/score/include/asm/checksum.h | 93 - arch/score/include/asm/io.h |1 - arch/score/include/asm/pgalloc.h |2 +- arch/score/kernel/entry.S |4 +- arch/score/kernel/process.c |4 +- 8 files changed, 64 insertions(+), 52 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[GIT PULL] S+core Architecture : fix bugs for compiling and support necessary functions
Hi Linus, Please pull these updates for S+core architecture. These updates include updating information of maintainers, fix some trivial errors, and add a necessary function for supporting ipv6. The following changes since commit bdbdfdef5766c2a60185e946df242f1bc0d37c09 Merge tag 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (Fri Sep 13 10:58:41 2013 -0700) on git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git For you to fetch changes up to 969f99168b9dff2f6cc07cdf14255178d4397c4f g...@github.com:sctscore/official-linux.git tags/branch-linus-20130914 Best, Lennox Wu --- Summary these commits: 1. Fix some trivial errors for successfully compiling the latest version Linux kernel. 2. Provide necessary function for support IPV6. 3. Update the information of maintainers. Lennox Wu (8): score : Update the information of Score maintainers score : Implement the function csum_ipv6_magic score : arch/score/kernel/entry.S: fix wrong instructions score : arch/score/kernel/process.c : fix some typos score : Modify the MAKEFILE of Score MAINTAINERS |4 +- arch/score/Kconfig|4 ++ arch/score/Makefile |4 +- arch/score/include/asm/checksum.h | 93 - arch/score/include/asm/io.h |1 - arch/score/include/asm/pgalloc.h |2 +- arch/score/kernel/entry.S |4 +- arch/score/kernel/process.c |4 +- 8 files changed, 64 insertions(+), 52 deletions(-) -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Remove support for score architecture
Before we start the development of the S+core, Sunplus had licensed ARM and MIPS. We develop S+core for other reason such as the price. Some products on the web of Sunplus adopt S+core , for example the SPV7050.(http://w3.sunplus.com/products/spv7050.asp) These products could still be bought from the market. Some high-end products adopt ARM or MIPS. So, there is no conflict for a company adopts multiple architectures. As I said, we recognize that we rarely update because of the limited applications and rare requests from customers. Maybe we don’t understand the culture enough; we think that it is unnecessary if we have no new bugs or new functions, the thought seems wrong. We can commit some patches in the near future. Best, Lennox 2013/9/2 Guenter Roeck : > On 09/01/2013 09:13 PM, Lennox Wu wrote: >> >> Dear all, >> >> Indeed, Sunplus S+core is not a popular architecture and there is no >> standalone to be sold so you should not find related news on the >> Internet. However, the s+core is adopted by our SoCs and these SoCs >> are indeed adopted by some companies, we hope the architecture can be >> reserved to provide the more and more powerful Linux for our >> customers. It is true that we rarely update the code because that we >> are rarely requested to add new functions and to correct bugs by our >> customers, and it is also because we have no new product to release. >> In the near future, we will release some patches for the existed >> S+core architecture. >> > > Key question is not if the platform is popular, but if it is maintained. > The commit log over the last two years strongly suggests that this is > not the case. I suspect that the code is far from compilable at this point, > much less executable. Unfortunately this is hard to verify, as a pre-built > or even buildable toolchain is not easily available. > > From a company perspective, you might want to decide if you want to put > resources into this architecture to keep it alive, or focus on more recent > chips and architectures. Information available on the internet suggests > that Suncore's more recent chips are based on ARM. Given that, it appears > somewhat unlikely that resources for maintaining S+core will be made > available. Guess we'll see if the situation changes. > > Guenter > > >> 2013/8/31 Guenter Roeck : >>> >>> The web site associated with the score architecture in MAINTAINERS >>> is non-functional and available for sale. The last Ack from one >>> of the maintainers was in December 2012. The main maintainer's last >>> commit was in 2011. The last maintainer pull request was early 2011. >>> >>> Cc: Lennox Wu >>> Cc: Chen Liqin >>> Signed-off-by: Guenter Roeck >>> --- >>> More housekeeping. >>> >>> Maybe this removal request is a bit early, but architecture support seems >>> to have vanished entirely. At the very least this puts interested parties >>> (if there are any) on notice. >>> > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Remove support for score architecture
Before we start the development of the S+core, Sunplus had licensed ARM and MIPS. We develop S+core for other reason such as the price. Some products on the web of Sunplus adopt S+core , for example the SPV7050.(http://w3.sunplus.com/products/spv7050.asp) These products could still be bought from the market. Some high-end products adopt ARM or MIPS. So, there is no conflict for a company adopts multiple architectures. As I said, we recognize that we rarely update because of the limited applications and rare requests from customers. Maybe we don’t understand the culture enough; we think that it is unnecessary if we have no new bugs or new functions, the thought seems wrong. We can commit some patches in the near future. Best, Lennox 2013/9/2 Guenter Roeck li...@roeck-us.net: On 09/01/2013 09:13 PM, Lennox Wu wrote: Dear all, Indeed, Sunplus S+core is not a popular architecture and there is no standalone to be sold so you should not find related news on the Internet. However, the s+core is adopted by our SoCs and these SoCs are indeed adopted by some companies, we hope the architecture can be reserved to provide the more and more powerful Linux for our customers. It is true that we rarely update the code because that we are rarely requested to add new functions and to correct bugs by our customers, and it is also because we have no new product to release. In the near future, we will release some patches for the existed S+core architecture. Key question is not if the platform is popular, but if it is maintained. The commit log over the last two years strongly suggests that this is not the case. I suspect that the code is far from compilable at this point, much less executable. Unfortunately this is hard to verify, as a pre-built or even buildable toolchain is not easily available. From a company perspective, you might want to decide if you want to put resources into this architecture to keep it alive, or focus on more recent chips and architectures. Information available on the internet suggests that Suncore's more recent chips are based on ARM. Given that, it appears somewhat unlikely that resources for maintaining S+core will be made available. Guess we'll see if the situation changes. Guenter 2013/8/31 Guenter Roeck li...@roeck-us.net: The web site associated with the score architecture in MAINTAINERS is non-functional and available for sale. The last Ack from one of the maintainers was in December 2012. The main maintainer's last commit was in 2011. The last maintainer pull request was early 2011. Cc: Lennox Wu lennox...@gmail.com Cc: Chen Liqin liqin.c...@sunplusct.com Signed-off-by: Guenter Roeck li...@roeck-us.net --- More housekeeping. Maybe this removal request is a bit early, but architecture support seems to have vanished entirely. At the very least this puts interested parties (if there are any) on notice. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
