mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stafford Horne <shorne@gmail.com>,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, openrisc@lists.librecores.org
Subject: Re: Add openrisc for-next branch to linux-next
Date: Thu, 1 Dec 2016 07:02:26 +0900 (JST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1612010658350.29569@lianli.shorne-pla.net> (raw)
In-Reply-To: <f7f0e124-00b9-5b21-9ca0-1f17e7c338bd@infradead.org>



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

  reply	other threads:[~2016-11-30 22:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 13:22 Stafford Horne
2016-11-30 18:38 ` Randy Dunlap
2016-11-30 22:02   ` Stafford Horne [this message]
     [not found]   ` <CAKaYPCMpZF6tQwQrtkVMZ1+F=vSUWxAx+skyMeU6FPPA_LGgVg@mail.gmail.com>
2016-11-30 22:05     ` [OpenRISC] " Randy Dunlap
2016-11-30 22:35       ` Stafford Horne
2016-11-30 21:35 ` Stephen Rothwell
2016-11-30 22:37   ` Stafford Horne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.20.1612010658350.29569@lianli.shorne-pla.net \
    --to=shorne@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®