Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1596562 > unrolled thread
| Started by | Masahiro Yamada <yamada.masahiro@socionext.com> |
|---|---|
| First post | 2017-03-10 03:10 +0100 |
| Last post | 2017-03-10 12:40 +0100 |
| Articles | 8 — 3 participants |
Back to article view | Back to linux.kernel
Kbuild maintainership Masahiro Yamada <yamada.masahiro@socionext.com> - 2017-03-10 03:10 +0100
Re: Kbuild maintainership Michal Marek <mmarek@suse.com> - 2017-03-10 09:50 +0100
Re: Kbuild maintainership Michal Marek <mmarek@suse.com> - 2017-03-10 11:20 +0100
Re: Kbuild maintainership Masahiro Yamada <yamada.masahiro@socionext.com> - 2017-03-10 11:40 +0100
Re: Kbuild maintainership Masahiro Yamada <yamada.masahiro@socionext.com> - 2017-03-11 06:50 +0100
Re: Kbuild maintainership Michal Marek <mmarek@suse.com> - 2017-03-13 11:50 +0100
Re: Kbuild maintainership Masahiro Yamada <yamada.masahiro@socionext.com> - 2017-03-10 11:30 +0100
Re: Kbuild maintainership Stephen Rothwell <sfr@canb.auug.org.au> - 2017-03-10 12:40 +0100
| From | Masahiro Yamada <yamada.masahiro@socionext.com> |
|---|---|
| Date | 2017-03-10 03:10 +0100 |
| Subject | Kbuild maintainership |
| Message-ID | <tjiae-5kk-9@gated-at.bofh.it> |
Hello Kbuild contributors, As you may notice, Michal has been busy since the beginning of this year, and it has been getting difficult for him to work on Kbuild on his regular basis. Michal sent me an email a few days ago, and we discussed this locally. Then, I decided to be a new maintainer of Kbuild. [1] Michal will stay as a maintainer too, but Kbuild patches will be primarily collected by me from this development cycle. I know many developers are looking forward to their patches picked up. I will try my best to help the community, and I just started to take a look. So, please wait a little more. If you have urgent problems, please speak up! Thanks! [1] https://patchwork.kernel.org/patch/9614477/ -- Best Regards Masahiro Yamada
[toc] | [next] | [standalone]
| From | Michal Marek <mmarek@suse.com> |
|---|---|
| Date | 2017-03-10 09:50 +0100 |
| Message-ID | <tjopj-1j2-9@gated-at.bofh.it> |
| In reply to | #1596562 |
Dne 10.3.2017 v 03:07 Masahiro Yamada napsal(a): > Hello Kbuild contributors, > > > As you may notice, Michal has been busy since the beginning > of this year, and it has been getting difficult for him to > work on Kbuild on his regular basis. Yes, that's unfortunately the case. > Michal sent me an email a few days ago, and we discussed this locally. > Then, I decided to be a new maintainer of Kbuild. [1] Thanks a lot for this and I wish you good luck with this new challenge. Michal
[toc] | [prev] | [next] | [standalone]
| From | Michal Marek <mmarek@suse.com> |
|---|---|
| Date | 2017-03-10 11:20 +0100 |
| Message-ID | <tjpOs-2xo-73@gated-at.bofh.it> |
| In reply to | #1596711 |
On 2017-03-10 10:17, Stephen Rothwell wrote: > I assume that I will get a request to change the kbuild-current and > kbuilt trees in linux-next soon. In the meantime, should I remove the > current ones? There is one genksyms fix in kbuild.git#kbuild which is not in mainline. Masahiro, can you please pull it into your tree and give Stephen the url and branches? Thanks, Michal
[toc] | [prev] | [next] | [standalone]
| From | Masahiro Yamada <yamada.masahiro@socionext.com> |
|---|---|
| Date | 2017-03-10 11:40 +0100 |
| Message-ID | <tjq7L-2G5-5@gated-at.bofh.it> |
| In reply to | #1597003 |
Hi Michal, 2017-03-10 19:15 GMT+09:00 Michal Marek <mmarek@suse.com>: > On 2017-03-10 10:17, Stephen Rothwell wrote: >> I assume that I will get a request to change the kbuild-current and >> kbuilt trees in linux-next soon. In the meantime, should I remove the >> current ones? > > There is one genksyms fix in kbuild.git#kbuild which is not in mainline. > Masahiro, can you please pull it into your tree and give Stephen the url > and branches? I have been wondering how itshould be handled. (and I had already sent a question about this to your suse.com address. I am guessing it has not reached to you, yet.) I will pull the branch into the new repository. Thanks! -- Best Regards Masahiro Yamada
[toc] | [prev] | [next] | [standalone]
| From | Masahiro Yamada <yamada.masahiro@socionext.com> |
|---|---|
| Date | 2017-03-11 06:50 +0100 |
| Message-ID | <tjI4F-6z3-3@gated-at.bofh.it> |
| In reply to | #1597003 |
Hi Michal, 2017-03-10 19:15 GMT+09:00 Michal Marek <mmarek@suse.com>: > On 2017-03-10 10:17, Stephen Rothwell wrote: >> I assume that I will get a request to change the kbuild-current and >> kbuilt trees in linux-next soon. In the meantime, should I remove the >> current ones? > > There is one genksyms fix in kbuild.git#kbuild which is not in mainline. > Masahiro, can you please pull it into your tree and give Stephen the url > and branches? Pulled into the (new) linux-kbuild/kbuild -- Best Regards Masahiro Yamada
[toc] | [prev] | [next] | [standalone]
| From | Michal Marek <mmarek@suse.com> |
|---|---|
| Date | 2017-03-13 11:50 +0100 |
| Message-ID | <tkvI7-7IV-25@gated-at.bofh.it> |
| In reply to | #1598262 |
On 2017-03-11 06:45, Masahiro Yamada wrote: > Hi Michal, > > 2017-03-10 19:15 GMT+09:00 Michal Marek <mmarek@suse.com>: >> On 2017-03-10 10:17, Stephen Rothwell wrote: >>> I assume that I will get a request to change the kbuild-current and >>> kbuilt trees in linux-next soon. In the meantime, should I remove the >>> current ones? >> >> There is one genksyms fix in kbuild.git#kbuild which is not in mainline. >> Masahiro, can you please pull it into your tree and give Stephen the url >> and branches? > > > Pulled into the (new) linux-kbuild/kbuild Thank you! Michal
[toc] | [prev] | [next] | [standalone]
| From | Masahiro Yamada <yamada.masahiro@socionext.com> |
|---|---|
| Date | 2017-03-10 11:30 +0100 |
| Message-ID | <tjpY6-2BJ-29@gated-at.bofh.it> |
| In reply to | #1596711 |
Hi Stephen, 2017-03-10 18:17 GMT+09:00 Stephen Rothwell <sfr@canb.auug.org.au>: > I assume that I will get a request to change the kbuild-current and > kbuilt trees in linux-next soon. In the meantime, should I remove the > current ones? > > No rush though since I am on leave next week. I had already dropped an email onto your address privately. (Maybe, are you checking the ML, but not your mailbox yet?) Anyway, no need to rush. When you get back to work, please adjust linux-next. Thanks! -- Best Regards Masahiro Yamada
[toc] | [prev] | [next] | [standalone]
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-03-10 12:40 +0100 |
| Message-ID | <tjpOs-2xo-75@gated-at.bofh.it> |
| In reply to | #1596711 |
Hi Michal, On Fri, 10 Mar 2017 09:48:44 +0100 Michal Marek <mmarek@suse.com> wrote: > > Dne 10.3.2017 v 03:07 Masahiro Yamada napsal(a): > > Hello Kbuild contributors, > > > > > > As you may notice, Michal has been busy since the beginning > > of this year, and it has been getting difficult for him to > > work on Kbuild on his regular basis. > > Yes, that's unfortunately the case. > > > > Michal sent me an email a few days ago, and we discussed this locally. > > Then, I decided to be a new maintainer of Kbuild. [1] > > Thanks a lot for this and I wish you good luck with this new challenge. I assume that I will get a request to change the kbuild-current and kbuilt trees in linux-next soon. In the meantime, should I remove the current ones? No rush though since I am on leave next week. -- Cheers, Stephen Rothwell
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web