Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #52839 > unrolled thread

Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Heinrich Schuchardt <xypron.glpk@gmx.de> - 2016-02-14 10:10 +0100
    Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Roger Shimizu <rogershimizu@gmail.com> - 2016-02-14 14:10 +0100
      Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Roger Shimizu <rogershimizu@gmail.com> - 2016-02-23 01:00 +0100
        Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Ben Hutchings <ben@decadent.org.uk> - 2016-02-23 02:10 +0100
          Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Roger Shimizu <rogershimizu@gmail.com> - 2016-02-23 18:00 +0100
            Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Ben Hutchings <ben@decadent.org.uk> - 2016-02-23 22:40 +0100
              Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Roger Shimizu <rogershimizu@gmail.com> - 2016-02-24 00:30 +0100
    Bug#813881: Bug#813893: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id Geert Stappers <stappers@stappers.nl> - 2016-02-14 17:50 +0100

#52839 — Bug#813881: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id

[Multipart message — attachments visible in raw view] — view raw

Shawn Guo the Linux kernel maintainer of ARM/Freescale IMX / MXC ARM
architecture has accepted my appended patch 0001-ARM... to change the
model id of the Wandboard Quad Rev B1 and the Wandboard Dual Rev B1.

See
https://lkml.org/lkml/2016/2/14/34
https://lkml.org/lkml/2016/2/7/270

I suggest to add the patch to
linux-source-4.3 (debian/patches/bugfix/arm)
and to update flash-kernel (patch 0001-db... appended).

Best regards

Heinrich Schuchardt

[toc] | [next] | [standalone]

#52841

Dear Kernel Maintainer,

On Sun, Feb 14, 2016 at 6:01 PM, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> Shawn Guo the Linux kernel maintainer of ARM/Freescale IMX / MXC ARM
> architecture has accepted my appended patch 0001-ARM... to change the
> model id of the Wandboard Quad Rev B1 and the Wandboard Dual Rev B1.
>
> See
> https://lkml.org/lkml/2016/2/14/34
> https://lkml.org/lkml/2016/2/7/270
>
> I suggest to add the patch to
> linux-source-4.3 (debian/patches/bugfix/arm)
> and to update flash-kernel (patch 0001-db... appended).

I also have a few device-tree "fixes", as well as "for-next" applied
by upstream sub-system maintainer.
For "fixes", some of those're already got merged into linus's 4.5-rc
tree, and will, AFAIK, be backported to each related/affected stable
kernel, and finally reach Debian's stable kernel; for "for-next", it's
waiting for the next merge window (to say, 4.6).

I also want to know what's debian's kernel policy [0] on backporting
those device-tree file.

Please help to clarify. Thank you!

[0]: https://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

[toc] | [prev] | [next] | [standalone]

#52991

Dear Ben,

On Sun, Feb 14, 2016 at 9:59 PM, Roger Shimizu <rogershimizu@gmail.com> wrote:
> Dear Kernel Maintainer,
>
> On Sun, Feb 14, 2016 at 6:01 PM, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>> Shawn Guo the Linux kernel maintainer of ARM/Freescale IMX / MXC ARM
>> architecture has accepted my appended patch 0001-ARM... to change the
>> model id of the Wandboard Quad Rev B1 and the Wandboard Dual Rev B1.
>>
>> See
>> https://lkml.org/lkml/2016/2/14/34
>> https://lkml.org/lkml/2016/2/7/270
>>
>> I suggest to add the patch to
>> linux-source-4.3 (debian/patches/bugfix/arm)
>> and to update flash-kernel (patch 0001-db... appended).
>
> I also have a few device-tree "fixes", as well as "for-next" applied
> by upstream sub-system maintainer.
> For "fixes", some of those're already got merged into linus's 4.5-rc
> tree, and will, AFAIK, be backported to each related/affected stable
> kernel, and finally reach Debian's stable kernel; for "for-next", it's
> waiting for the next merge window (to say, 4.6).
>
> I also want to know what's debian's kernel policy [0] on backporting
> those device-tree file.
>
> Please help to clarify. Thank you!
>
> [0]: https://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines

Could you help to comment on this, please?

If you think backporting those device-tree to "master"/"sid" is fine,
I can handle both the patch mention in this thread and a few
Linkstation device-tree patch I submitted.
Thank you!

-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

[toc] | [prev] | [next] | [standalone]

#52995

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2016-02-23 at 08:11 +0900, Roger Shimizu wrote:
> Dear Ben,
> 
> On Sun, Feb 14, 2016 at 9:59 PM, Roger Shimizu  wrote:
> > Dear Kernel Maintainer,
> > 
> > On Sun, Feb 14, 2016 at 6:01 PM, Heinrich Schuchardt  wrote:
> > > Shawn Guo the Linux kernel maintainer of ARM/Freescale IMX / MXC ARM
> > > architecture has accepted my appended patch 0001-ARM... to change the
> > > model id of the Wandboard Quad Rev B1 and the Wandboard Dual Rev B1.
> > > 
> > > See
> > > https://lkml.org/lkml/2016/2/14/34
> > > https://lkml.org/lkml/2016/2/7/270
> > > 
> > > I suggest to add the patch to
> > > linux-source-4.3 (debian/patches/bugfix/arm)
> > > and to update flash-kernel (patch 0001-db... appended).
> > 
> > I also have a few device-tree "fixes", as well as "for-next" applied
> > by upstream sub-system maintainer.
> > For "fixes", some of those're already got merged into linus's 4.5-rc
> > tree, and will, AFAIK, be backported to each related/affected stable
> > kernel, and finally reach Debian's stable kernel; for "for-next", it's
> > waiting for the next merge window (to say, 4.6).
> > 
> > I also want to know what's debian's kernel policy [0] on backporting
> > those device-tree file.
> > 
> > Please help to clarify. Thank you!
> > 
> > [0]: https://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines
> 
> Could you help to comment on this, please?
> 
> If you think backporting those device-tree to "master"/"sid" is fine,
> I can handle both the patch mention in this thread and a few
> Linkstation device-tree patch I submitted.

Yes, this is all fine for sid.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.

[toc] | [prev] | [next] | [standalone]

#53002

Dear Ben,

On Tue, Feb 23, 2016 at 9:53 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Tue, 2016-02-23 at 08:11 +0900, Roger Shimizu wrote:
>> If you think backporting those device-tree to "master"/"sid" is fine,
>> I can handle both the patch mention in this thread and a few
>> Linkstation device-tree patch I submitted.
>
> Yes, this is all fine for sid.

Thank you!
I pushed a commit to "rosh/sid" branch.
Please help to review since it's my first time to applying patch.
If nothing wrong, I'll push to sid branch afterwards.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

[toc] | [prev] | [next] | [standalone]

#53004

[Multipart message — attachments visible in raw view] — view raw

On Wed, 2016-02-24 at 01:50 +0900, Roger Shimizu wrote:
> Dear Ben,
> 
> On Tue, Feb 23, 2016 at 9:53 AM, Ben Hutchings <ben@decadent.org.uk>
> wrote:
> > On Tue, 2016-02-23 at 08:11 +0900, Roger Shimizu wrote:
> > > If you think backporting those device-tree to "master"/"sid" is
> > > fine,
> > > I can handle both the patch mention in this thread and a few
> > > Linkstation device-tree patch I submitted.
> > 
> > Yes, this is all fine for sid.
> 
> Thank you!
> I pushed a commit to "rosh/sid" branch.
> Please help to review since it's my first time to applying patch.
> If nothing wrong, I'll push to sid branch afterwards.

You didn't commit the update to debian/patches/series.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.

[toc] | [prev] | [next] | [standalone]

#53006

Control: tags + fixed pending

On Wed, Feb 24, 2016 at 6:28 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Wed, 2016-02-24 at 01:50 +0900, Roger Shimizu wrote:
>> Thank you!
>> I pushed a commit to "rosh/sid" branch.
>> Please help to review since it's my first time to applying patch.
>> If nothing wrong, I'll push to sid branch afterwards.
>
> You didn't commit the update to debian/patches/series.

Sorry about that.
Fixed and pushed to sid branch.
Confirmed OK by "debian/rules orig" command. It's enough because it's
just a device-tree patch.

Thanks for your guiding!

-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

[toc] | [prev] | [next] | [standalone]

#52844 — Bug#813881: Bug#813893: [PATCH 1/1 v3] ARM: dts: imx6dlq-wandboard-revb1.dts: use unique model id

Control: tag -1 patch

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web