Message ID | 459c0bad-c02e-40f0-9e56-1dcdad9c6591.lettre@localhost (mailing list archive) |
---|---|
State | Queued, archived |
Commit | 2269f0c15191af317d64115176a01bf303532af3 |
Headers | show |
Series | [GIT,PULL] Allwinner Device Tree Changes for 5.3 | expand |
On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote: > Hi, > > Please pull the following changes for the next release. > > Thanks! > Maxime > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) > > are available in the Git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807 You know, there's a timestamp in the tag too, no need to encode it in the name. > > for you to fetch changes up to 2269f0c15191af317d64115176a01bf303532af3: > > dt-bindings: pwm: Convert Allwinner PWM to a schema (2019-06-21 09:59:10 +0200) > > ---------------------------------------------------------------- > Our usual bunch of patches: > - Some work on the BPi M2-Berry to support various devices > - Convert some bindings to a schema, and a lot of fixes reported by > the schemas we introduced. > - A few other fixes here and there Merged, thanks. -Olof
Hi Olof, On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote: > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote: > > Hi, > > > > Please pull the following changes for the next release. > > > > Thanks! > > Maxime > > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: > > > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) > > > > are available in the Git repository at: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807 > > You know, there's a timestamp in the tag too, no need to encode it in the name. Yeah, I've switched to some tooling to send them instead of doing them manually, and having a timestamp was the easiest solution to avoid a collision, but I guess having it down to the minute was a bit overkill. Do you have any preference on this? Thanks! Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > Hi Olof, > > On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote: > > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote: > > > Hi, > > > > > > Please pull the following changes for the next release. > > > > > > Thanks! > > > Maxime > > > > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: > > > > > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) > > > > > > are available in the Git repository at: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807 > > > > You know, there's a timestamp in the tag too, no need to encode it in the name. > > Yeah, I've switched to some tooling to send them instead of doing them > manually, and having a timestamp was the easiest solution to avoid a > collision, but I guess having it down to the minute was a bit > overkill. Do you have any preference on this? Main thing for me is that I can't tell from time timestamps if it's a respin/new version, or a re-stamp, i.e. if it's something I should care about or not. I.e. it doesn't carry any useful signal for the consuming side and is mostly noise. -Olof
On Tue, Jun 25, 2019 at 02:36:30PM +0200, Olof Johansson wrote: > On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > > > Hi Olof, > > > > On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote: > > > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote: > > > > Hi, > > > > > > > > Please pull the following changes for the next release. > > > > > > > > Thanks! > > > > Maxime > > > > > > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: > > > > > > > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) > > > > > > > > are available in the Git repository at: > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807 > > > > > > You know, there's a timestamp in the tag too, no need to encode it in the name. > > > > Yeah, I've switched to some tooling to send them instead of doing them > > manually, and having a timestamp was the easiest solution to avoid a > > collision, but I guess having it down to the minute was a bit > > overkill. Do you have any preference on this? > > Main thing for me is that I can't tell from time timestamps if it's a > respin/new version, or a re-stamp, i.e. if it's something I should > care about or not. > > I.e. it doesn't carry any useful signal for the consuming side and is > mostly noise. Ok, so you'd prefer something like <tag>, <tag>-2 if there's multiple, subsequent, PR, and <tag>, <tag>-again if the latter replaces the former? Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
On Tue, Jun 25, 2019 at 10:55 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > On Tue, Jun 25, 2019 at 02:36:30PM +0200, Olof Johansson wrote: > > On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > > > > > Hi Olof, > > > > > > On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote: > > > > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote: > > > > > Hi, > > > > > > > > > > Please pull the following changes for the next release. > > > > > > > > > > Thanks! > > > > > Maxime > > > > > > > > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: > > > > > > > > > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) > > > > > > > > > > are available in the Git repository at: > > > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807 > > > > > > > > You know, there's a timestamp in the tag too, no need to encode it in the name. > > > > > > Yeah, I've switched to some tooling to send them instead of doing them > > > manually, and having a timestamp was the easiest solution to avoid a > > > collision, but I guess having it down to the minute was a bit > > > overkill. Do you have any preference on this? > > > > Main thing for me is that I can't tell from time timestamps if it's a > > respin/new version, or a re-stamp, i.e. if it's something I should > > care about or not. > > > > I.e. it doesn't carry any useful signal for the consuming side and is > > mostly noise. > > Ok, so you'd prefer something like <tag>, <tag>-2 if there's multiple, > subsequent, PR, and <tag>, <tag>-again if the latter replaces the former? Yeah, that's what a lot of other maintainers do and it's something that's been working pretty well. Sometimes they use -v2 at the end for respins, i.e. dt-2-v2 etc. I recommend deleting respun tags so we don't accidentally merge them (if we didn't see the follow-up). -Olof
On Thu, Jun 27, 2019 at 10:09:53AM +0800, Olof Johansson wrote: > On Tue, Jun 25, 2019 at 10:55 PM Maxime Ripard > <maxime.ripard@bootlin.com> wrote: > > > > On Tue, Jun 25, 2019 at 02:36:30PM +0200, Olof Johansson wrote: > > > On Tue, Jun 25, 2019 at 2:32 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > > > > > > > Hi Olof, > > > > > > > > On Tue, Jun 25, 2019 at 04:41:19AM -0700, Olof Johansson wrote: > > > > > On Fri, Jun 21, 2019 at 10:08:08AM +0200, Maxime Ripard wrote: > > > > > > Hi, > > > > > > > > > > > > Please pull the following changes for the next release. > > > > > > > > > > > > Thanks! > > > > > > Maxime > > > > > > > > > > > > The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9: > > > > > > > > > > > > Linux 5.2-rc1 (2019-05-19 15:47:09 -0700) > > > > > > > > > > > > are available in the Git repository at: > > > > > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.3-201906210807 > > > > > > > > > > You know, there's a timestamp in the tag too, no need to encode it in the name. > > > > > > > > Yeah, I've switched to some tooling to send them instead of doing them > > > > manually, and having a timestamp was the easiest solution to avoid a > > > > collision, but I guess having it down to the minute was a bit > > > > overkill. Do you have any preference on this? > > > > > > Main thing for me is that I can't tell from time timestamps if it's a > > > respin/new version, or a re-stamp, i.e. if it's something I should > > > care about or not. > > > > > > I.e. it doesn't carry any useful signal for the consuming side and is > > > mostly noise. > > > > Ok, so you'd prefer something like <tag>, <tag>-2 if there's multiple, > > subsequent, PR, and <tag>, <tag>-again if the latter replaces the former? > > Yeah, that's what a lot of other maintainers do and it's something > that's been working pretty well. > > Sometimes they use -v2 at the end for respins, i.e. dt-2-v2 etc. I > recommend deleting respun tags so we don't accidentally merge them (if > we didn't see the follow-up). Ok, I'll adjust my program to do so next time then, thanks! Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com