| Message ID | 20171031202357.GA1030@ziepe.ca (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On Tue, Oct 31, 2017 at 02:23:57PM -0600, Jason Gunthorpe wrote: > My email address for open source work is moving to this new permanent > personal address. > > Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> > --- > MAINTAINERS | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 6671f375f7fcdd..b79eb071475ffc 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER > M: Peter Huewe <peterhuewe@gmx.de> > M: Marcel Selhorst <tpmdd@selhorst.net> > M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> > +R: Jason Gunthorpe <jgg@ziepe.ca> > W: http://tpmdd.sourceforge.net > L: tpmdd-devel@lists.sourceforge.net (moderated for non-subscribers) > Q: https://patchwork.kernel.org/project/tpmdd-devel/list/ > -- > 2.7.4 > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> Should these updates go to my tree? I posted previous update to linux-kernel@vger.kernel.org. /Jarkko
Am 3. November 2017 15:28:41 MEZ schrieb Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>: >On Tue, Oct 31, 2017 at 02:23:57PM -0600, Jason Gunthorpe wrote: >> My email address for open source work is moving to this new permanent >> personal address. >> >> Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> >> --- >> MAINTAINERS | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/MAINTAINERS b/MAINTAINERS >> index 6671f375f7fcdd..b79eb071475ffc 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER >> M: Peter Huewe <peterhuewe@gmx.de> >> M: Marcel Selhorst <tpmdd@selhorst.net> >> M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> >> -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> >> +R: Jason Gunthorpe <jgg@ziepe.ca> >> W: http://tpmdd.sourceforge.net >> L: tpmdd-devel@lists.sourceforge.net (moderated for non-subscribers) >> Q: https://patchwork.kernel.org/project/tpmdd-devel/list/ >> -- >> 2.7.4 >> > >Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > >Should these updates go to my tree? I posted previous update to >linux-kernel@vger.kernel.org. Which equals /dev/null for most cases. Why shouldn'tit go through your tree? It's a maintainers update for your subsystem - and you did it in the past when modifying the urls. >/Jarkko
On Fri, Nov 03, 2017 at 05:05:49PM +0100, Peter Huewe wrote: > > > Am 3. November 2017 15:28:41 MEZ schrieb Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>: > >On Tue, Oct 31, 2017 at 02:23:57PM -0600, Jason Gunthorpe wrote: > >> My email address for open source work is moving to this new permanent > >> personal address. > >> > >> Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> > >> --- > >> MAINTAINERS | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/MAINTAINERS b/MAINTAINERS > >> index 6671f375f7fcdd..b79eb071475ffc 100644 > >> --- a/MAINTAINERS > >> +++ b/MAINTAINERS > >> @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER > >> M: Peter Huewe <peterhuewe@gmx.de> > >> M: Marcel Selhorst <tpmdd@selhorst.net> > >> M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > >> -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> > >> +R: Jason Gunthorpe <jgg@ziepe.ca> > >> W: http://tpmdd.sourceforge.net > >> L: tpmdd-devel@lists.sourceforge.net (moderated for non-subscribers) > >> Q: https://patchwork.kernel.org/project/tpmdd-devel/list/ > >> -- > >> 2.7.4 > >> > > > >Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > > > >Should these updates go to my tree? I posted previous update to > >linux-kernel@vger.kernel.org. > Which equals /dev/null for most cases. > > Why shouldn'tit go through your tree? > It's a maintainers update for your subsystem - and you did it in the past when modifying the urls. > > >/Jarkko > > -- > Sent from my mobile I applied two patches to my tree. /Jarkko
On Tue, Nov 07, 2017 at 05:03:56PM +0200, Jarkko Sakkinen wrote: > On Fri, Nov 03, 2017 at 05:05:49PM +0100, Peter Huewe wrote: > > > > > > Am 3. November 2017 15:28:41 MEZ schrieb Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>: > > >On Tue, Oct 31, 2017 at 02:23:57PM -0600, Jason Gunthorpe wrote: > > >> My email address for open source work is moving to this new permanent > > >> personal address. > > >> > > >> Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> > > >> --- > > >> MAINTAINERS | 2 +- > > >> 1 file changed, 1 insertion(+), 1 deletion(-) > > >> > > >> diff --git a/MAINTAINERS b/MAINTAINERS > > >> index 6671f375f7fcdd..b79eb071475ffc 100644 > > >> --- a/MAINTAINERS > > >> +++ b/MAINTAINERS > > >> @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER > > >> M: Peter Huewe <peterhuewe@gmx.de> > > >> M: Marcel Selhorst <tpmdd@selhorst.net> > > >> M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > > >> -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> > > >> +R: Jason Gunthorpe <jgg@ziepe.ca> > > >> W: http://tpmdd.sourceforge.net > > >> L: tpmdd-devel@lists.sourceforge.net (moderated for non-subscribers) > > >> Q: https://patchwork.kernel.org/project/tpmdd-devel/list/ > > >> -- > > >> 2.7.4 > > >> > > > > > >Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > > > > > >Should these updates go to my tree? I posted previous update to > > >linux-kernel@vger.kernel.org. > > Which equals /dev/null for most cases. > > > > Why shouldn'tit go through your tree? > > It's a maintainers update for your subsystem - and you did it in the past when modifying the urls. > > > > >/Jarkko > > > > -- > > Sent from my mobile > > I applied two patches to my tree. > > /Jarkko NAK linux-kernel@vger.kernel.org is missing *completely*. It should be at minimum in the CC field. My previous update did not go through my tree. I misread your original response to say that I should put also URL update to my tree. I did. It resulted a merge conflict. Updating that file goes out of my territory other than acking the updates. Now that linux-kernel is missing this completely unacceptable. /Jarkko
Am 8. November 2017 07:36:40 MEZ schrieb Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>: >On Tue, Nov 07, 2017 at 05:03:56PM +0200, Jarkko Sakkinen wrote: >> On Fri, Nov 03, 2017 at 05:05:49PM +0100, Peter Huewe wrote: >> > >> > >> > Am 3. November 2017 15:28:41 MEZ schrieb Jarkko Sakkinen ><jarkko.sakkinen@linux.intel.com>: >> > >On Tue, Oct 31, 2017 at 02:23:57PM -0600, Jason Gunthorpe wrote: >> > >> My email address for open source work is moving to this new >permanent >> > >> personal address. >> > >> >> > >> Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> >> > >> --- >> > >> MAINTAINERS | 2 +- >> > >> 1 file changed, 1 insertion(+), 1 deletion(-) >> > >> >> > >> diff --git a/MAINTAINERS b/MAINTAINERS >> > >> index 6671f375f7fcdd..b79eb071475ffc 100644 >> > >> --- a/MAINTAINERS >> > >> +++ b/MAINTAINERS >> > >> @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER >> > >> M: Peter Huewe <peterhuewe@gmx.de> >> > >> M: Marcel Selhorst <tpmdd@selhorst.net> >> > >> M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> >> > >> -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> >> > >> +R: Jason Gunthorpe <jgg@ziepe.ca> >> > >> W: http://tpmdd.sourceforge.net >> > >> L: tpmdd-devel@lists.sourceforge.net (moderated for >non-subscribers) >> > >> Q: https://patchwork.kernel.org/project/tpmdd-devel/list/ >> > >> -- >> > >> 2.7.4 >> > >> >> > > >> > >Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> >> > > >> > >Should these updates go to my tree? I posted previous update to >> > >linux-kernel@vger.kernel.org. >> > Which equals /dev/null for most cases. >> > >> > Why shouldn'tit go through your tree? >> > It's a maintainers update for your subsystem - and you did it in >the past when modifying the urls. >> > >> > >/Jarkko >> > >> > -- >> > Sent from my mobile >> >> I applied two patches to my tree. >> >> /Jarkko > >NAK > NAK what? Who/what do you nak to? >linux-kernel@vger.kernel.org is missing *completely*. It should be at >minimum in the CC field. > >My previous update did not go through my tree. I misread your original >response to say that I should put also URL update to my tree. I did. >It resulted a merge conflict. > I do not understand what you are saying. Please rephrase/clarify. >Updating that file goes out of my territory other than acking the >updates. Imho not really, since there is no MAINTAINERS maintainer. If you feel uncomfortable with adding the changes to MAINTAINERS via your tree, please ask James to pull them up - just as Mimi did for her linux-integrity update. >Now that linux-kernel is missing this completely unacceptable. > >/Jarkko
On Wed, Nov 08, 2017 at 10:27:37AM +0100, Peter Huewe wrote: > >Updating that file goes out of my territory other than acking the > >updates. > Imho not really, since there is no MAINTAINERS maintainer. If you > feel uncomfortable with adding the changes to MAINTAINERS via your > tree, please ask James to pull them up - just as Mimi did for her > linux-integrity update. Agreed, if you are submitting pull requests then the MAINTAINERS update for TPM related things should go into your pull request. That is appropriate.. It isn't necessary for everything to be cc'd everywhere, ultimately it is your responsibility as the TPM maintainer to accept/reject this change. If it was a larger change, like adding/removing a maintainer then a large audiance would be appropriate, but this is just changing spelling and the patch was PGP signed .. Jason
On Wed, Nov 08, 2017 at 10:27:37AM +0100, Peter Huewe wrote: > > > Am 8. November 2017 07:36:40 MEZ schrieb Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>: > >On Tue, Nov 07, 2017 at 05:03:56PM +0200, Jarkko Sakkinen wrote: > >> On Fri, Nov 03, 2017 at 05:05:49PM +0100, Peter Huewe wrote: > >> > > >> > > >> > Am 3. November 2017 15:28:41 MEZ schrieb Jarkko Sakkinen > ><jarkko.sakkinen@linux.intel.com>: > >> > >On Tue, Oct 31, 2017 at 02:23:57PM -0600, Jason Gunthorpe wrote: > >> > >> My email address for open source work is moving to this new > >permanent > >> > >> personal address. > >> > >> > >> > >> Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> > >> > >> --- > >> > >> MAINTAINERS | 2 +- > >> > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> > >> > >> diff --git a/MAINTAINERS b/MAINTAINERS > >> > >> index 6671f375f7fcdd..b79eb071475ffc 100644 > >> > >> --- a/MAINTAINERS > >> > >> +++ b/MAINTAINERS > >> > >> @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER > >> > >> M: Peter Huewe <peterhuewe@gmx.de> > >> > >> M: Marcel Selhorst <tpmdd@selhorst.net> > >> > >> M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > >> > >> -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> > >> > >> +R: Jason Gunthorpe <jgg@ziepe.ca> > >> > >> W: http://tpmdd.sourceforge.net > >> > >> L: tpmdd-devel@lists.sourceforge.net (moderated for > >non-subscribers) > >> > >> Q: https://patchwork.kernel.org/project/tpmdd-devel/list/ > >> > >> -- > >> > >> 2.7.4 > >> > >> > >> > > > >> > >Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > >> > > > >> > >Should these updates go to my tree? I posted previous update to > >> > >linux-kernel@vger.kernel.org. > >> > Which equals /dev/null for most cases. > >> > > >> > Why shouldn'tit go through your tree? > >> > It's a maintainers update for your subsystem - and you did it in > >the past when modifying the urls. > >> > > >> > >/Jarkko > >> > > >> > -- > >> > Sent from my mobile > >> > >> I applied two patches to my tree. > >> > >> /Jarkko > > > >NAK > > > NAK what? > Who/what do you nak to? > > >linux-kernel@vger.kernel.org is missing *completely*. It should be at > >minimum in the CC field. > > > >My previous update did not go through my tree. I misread your original > >response to say that I should put also URL update to my tree. I did. > >It resulted a merge conflict. > > > I do not understand what you are saying. > Please rephrase/clarify. > > >Updating that file goes out of my territory other than acking the > >updates. > Imho not really, since there is no MAINTAINERS maintainer. > If you feel uncomfortable with adding the changes to MAINTAINERS via > your tree, please ask James to pull them up - just as Mimi did for her > linux-integrity update. I'm just saying that the previous update did not go my tree but I can queue this one to my tree given your comments. I just have to wait up until the previous MAINTAINERS update is visible in the security tree. /Jarkko
On Wed, Nov 08, 2017 at 03:24:34PM -0700, Jason Gunthorpe wrote: > On Wed, Nov 08, 2017 at 10:27:37AM +0100, Peter Huewe wrote: > > > >Updating that file goes out of my territory other than acking the > > >updates. > > > Imho not really, since there is no MAINTAINERS maintainer. If you > > feel uncomfortable with adding the changes to MAINTAINERS via your > > tree, please ask James to pull them up - just as Mimi did for her > > linux-integrity update. > > Agreed, if you are submitting pull requests then the MAINTAINERS > update for TPM related things should go into your pull request. That > is appropriate.. > > It isn't necessary for everything to be cc'd everywhere, ultimately it > is your responsibility as the TPM maintainer to accept/reject this > change. > > If it was a larger change, like adding/removing a maintainer then a > large audiance would be appropriate, but this is just changing > spelling and the patch was PGP signed .. > > Jason Agreed. I'll apply this after my previous change is available. /Jarkko
diff --git a/MAINTAINERS b/MAINTAINERS index 6671f375f7fcdd..b79eb071475ffc 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -13588,7 +13588,7 @@ TPM DEVICE DRIVER M: Peter Huewe <peterhuewe@gmx.de> M: Marcel Selhorst <tpmdd@selhorst.net> M: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> -R: Jason Gunthorpe <jgunthorpe@obsidianresearch.com> +R: Jason Gunthorpe <jgg@ziepe.ca> W: http://tpmdd.sourceforge.net L: tpmdd-devel@lists.sourceforge.net (moderated for non-subscribers) Q: https://patchwork.kernel.org/project/tpmdd-devel/list/
My email address for open source work is moving to this new permanent personal address. Signed-off-by: Jason Gunthorpe <jgunthorpe@ziepe.ca> --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)