Add openrisc for-next branch to linux-next

Add openrisc for-next branch to linux-next

[Stafford Horne]

Hi Stephen,

I have been working on getting the OpenRISC backlog of fixes sorted out 
for upstream.  Can this branch be added to linux-next?

   git://github.com/openrisc/linux.git for-next

These have been through a few reviews and we plan to ask Linus to pull in 
the next merge window.

-Stafford

Re: Add openrisc for-next branch to linux-next

[Randy Dunlap]

On 11/30/16 05:22, Stafford Horne wrote:
> Hi Stephen,
> 
> I have been working on getting the OpenRISC backlog of fixes sorted out for upstream.  Can this branch be added to linux-next?
> 
>   git://github.com/openrisc/linux.git for-next
> 
> These have been through a few reviews and we plan to ask Linus to pull in the next merge window.
> 
> -Stafford

Hi,

I see that you have updated MAINTAINERS.  Good.

Does openRISC support VGA console?
I tried to send a patch to Jason a few days ago.
Please look at http://marc.info/?l=linux-kernel&m=147968525011508&w=2
(or I can resend it if you wish).

The kbuild test bot has been reporting this build error for several
months.  If my fix is wrong, please submit something else.

Thanks.
-- 
~Randy

Re: Add openrisc for-next branch to linux-next

[Stafford Horne]

On Wed, 30 Nov 2016, Randy Dunlap wrote:

> On 11/30/16 05:22, Stafford Horne wrote:
>> Hi Stephen,
>>
>> I have been working on getting the OpenRISC backlog of fixes sorted out for upstream.  Can this branch be added to linux-next?
>>
>>   git://github.com/openrisc/linux.git for-next
>>
>> These have been through a few reviews and we plan to ask Linus to pull in the next merge window.
>>
>> -Stafford
>
> Hi,
>
> I see that you have updated MAINTAINERS.  Good.
>
> Does openRISC support VGA console?
> I tried to send a patch to Jason a few days ago.
> Please look at http://marc.info/?l=linux-kernel&m=147968525011508&w=2
> (or I can resend it if you wish).
>
> The kbuild test bot has been reporting this build error for several
> months.  If my fix is wrong, please submit something else.

Hi Randy,

I was watching that thread, I honestly thought it would have been pulled 
in by one of the console maintainers.

Openrisc does not have support for vga console, some people may have 
hacked something together, but its not in our kernel yet.  So I have no 
issue disabling it in the build.

I will pull it in to my branch.

If someone else pulls,
Acked-by: Stafford Horne <shorne@gmail.com>

-Stafford

Re: [OpenRISC] Add openrisc for-next branch to linux-next

[Randy Dunlap]

On 11/30/16 12:11, Olof Kindgren wrote:
> 
>     Hi,
> 
>     I see that you have updated MAINTAINERS.  Good.
> 
>     Does openRISC support VGA console?
>     I tried to send a patch to Jason a few days ago.
>     Please look at http://marc.info/?l=linux-kernel&m=147968525011508&w=2 <http://marc.info/?l=linux-kernel&m=147968525011508&w=2>
>     (or I can resend it if you wish).
> 
>     The kbuild test bot has been reporting this build error for several
>     months.  If my fix is wrong, please submit something else.
> 
>     Thanks.
>     --
>     ~Randy
>     _______________________________________________
>     OpenRISC mailing list
>     OpenRISC@lists.librecores.org <mailto:OpenRISC@lists.librecores.org>
>     https://lists.librecores.org/listinfo/openrisc <https://lists.librecores.org/listinfo/openrisc>
> 
> 
> Hi Randy,
> 
> This is a known issue. This patch (https://github.com/openrisc/linux/pull/5) should take care of it. Can't say if it's the correct solution though, but it works both with and without a VGA console
> 
> //Olof

Thanks.


-- 
~Randy

Re: [OpenRISC] Add openrisc for-next branch to linux-next

[Stafford Horne]

On Wed, 30 Nov 2016, Randy Dunlap wrote:

> On 11/30/16 12:11, Olof Kindgren wrote:
>>
>>     Hi,
>>
>>     I see that you have updated MAINTAINERS.  Good.
>>
>>     Does openRISC support VGA console?
>>     I tried to send a patch to Jason a few days ago.
>>     Please look at http://marc.info/?l=linux-kernel&m=147968525011508&w=2 <http://marc.info/?l=linux-kernel&m=147968525011508&w=2>
>>     (or I can resend it if you wish).
>>
>>     The kbuild test bot has been reporting this build error for several
>>     months.  If my fix is wrong, please submit something else.
>>
>>     Thanks.
>>     --
>>     ~Randy
>>     _______________________________________________
>>     OpenRISC mailing list
>>     OpenRISC@lists.librecores.org <mailto:OpenRISC@lists.librecores.org>
>>     https://lists.librecores.org/listinfo/openrisc <https://lists.librecores.org/listinfo/openrisc>
>>
>>
>> Hi Randy,
>>
>> This is a known issue. This patch (https://github.com/openrisc/linux/pull/5) should take care of it. Can't say if it's the correct solution though, but it works both with and without a VGA console
>>
>> //Olof
>
> Thanks.

Hello,

I think I will take Randy's patch instead.  The patch above defines 
screen_info, but I am not sure if it has been used or if anyone has got 
vga consoles working on openrisc.

We can always add vga console support if someone has the hardware and can 
test it. It will be harder to take it away.

-Stafford

Re: Add openrisc for-next branch to linux-next

[Stephen Rothwell]

Hi Stafford,

On Wed, 30 Nov 2016 22:22:41 +0900 (JST) Stafford Horne <shorne@gmail.com> wrote:
>
> I have been working on getting the OpenRISC backlog of fixes sorted out 
> for upstream.  Can this branch be added to linux-next?
> 
>    git://github.com/openrisc/linux.git for-next
> 
> These have been through a few reviews and we plan to ask Linus to pull in 
> the next merge window.

Added from today.

Just a note: your top commits has no Signed-off-by from you as the committer ...

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Re: Add openrisc for-next branch to linux-next

[Stafford Horne]

On Thu, 1 Dec 2016, Stephen Rothwell wrote:

> Hi Stafford,
>
> On Wed, 30 Nov 2016 22:22:41 +0900 (JST) Stafford Horne <shorne@gmail.com> wrote:
>>
>> I have been working on getting the OpenRISC backlog of fixes sorted out
>> for upstream.  Can this branch be added to linux-next?
>>
>>    git://github.com/openrisc/linux.git for-next
>>
>> These have been through a few reviews and we plan to ask Linus to pull in
>> the next merge window.
>
> Added from today.
>
> Just a note: your top commits has no Signed-off-by from you as the committer ...

Hello,

Right I had been adding those as part of the `git send-email` phase but I 
realize I do need them in git now. Sorry about that.

> Thanks for adding your subsystem tree as a participant of linux-next.  As
> you may know, this is not a judgement of your code.  The purpose of
> linux-next is for integration testing and to lower the impact of
> conflicts between subsystems in the next merge window.
>
> You will need to ensure that the patches/commits in your tree/series have
> been:
>     * submitted under GPL v2 (or later) and include the Contributor's
>        Signed-off-by,
>     * posted to the relevant mailing list,
>     * reviewed by you (or another maintainer of your subsystem tree),
>     * successfully unit tested, and
>     * destined for the current or next Linux merge window.
>
> Basically, this should be just what you would send to Linus (or ask him
> to fetch).  It is allowed to be rebased if you deem it necessary.

Thank You,

-Stafford