All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-mips@vger.kernel.org
Subject: Re: [PATCH] newport_con: vc_color is now in state
Date: Fri, 24 Jul 2020 12:30:58 +0200	[thread overview]
Message-ID: <92c429c6-5cce-b5cc-877e-d4784651e31f@suse.cz> (raw)
In-Reply-To: <b1b9d90a-5fe3-947a-dc4e-8576cd143869@gmail.com>

On 24. 07. 20, 11:30, Sergei Shtylyov wrote:
> On 24.07.2020 9:27, Jiri Slaby wrote:
> 
>> Since commit 28bc24fc46f9 (vc: separate state), vc->vc_color is known as
> 
>    Cgit says "Bad object id: 28bc24fc46f9" (in Linus' repo).

That's because it's not in Linus' repo yet.

-- 
js
suse labs

WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jslaby@suse.cz>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-fbdev@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-mips@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] newport_con: vc_color is now in state
Date: Fri, 24 Jul 2020 10:30:58 +0000	[thread overview]
Message-ID: <92c429c6-5cce-b5cc-877e-d4784651e31f@suse.cz> (raw)
In-Reply-To: <b1b9d90a-5fe3-947a-dc4e-8576cd143869@gmail.com>

On 24. 07. 20, 11:30, Sergei Shtylyov wrote:
> On 24.07.2020 9:27, Jiri Slaby wrote:
> 
>> Since commit 28bc24fc46f9 (vc: separate state), vc->vc_color is known as
> 
>    Cgit says "Bad object id: 28bc24fc46f9" (in Linus' repo).

That's because it's not in Linus' repo yet.

-- 
js
suse labs

WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jslaby@suse.cz>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-fbdev@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	linux-mips@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] newport_con: vc_color is now in state
Date: Fri, 24 Jul 2020 12:30:58 +0200	[thread overview]
Message-ID: <92c429c6-5cce-b5cc-877e-d4784651e31f@suse.cz> (raw)
In-Reply-To: <b1b9d90a-5fe3-947a-dc4e-8576cd143869@gmail.com>

On 24. 07. 20, 11:30, Sergei Shtylyov wrote:
> On 24.07.2020 9:27, Jiri Slaby wrote:
> 
>> Since commit 28bc24fc46f9 (vc: separate state), vc->vc_color is known as
> 
>    Cgit says "Bad object id: 28bc24fc46f9" (in Linus' repo).

That's because it's not in Linus' repo yet.

-- 
js
suse labs
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-07-24 10:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24  5:57 [linux-next:master 2417/10784] drivers/video/console/newport_con.c:362:15: error: 'struct vc_data' has no member named 'vc_color'; did you mean kernel test robot
2020-07-24  6:27 ` [PATCH] newport_con: vc_color is now in state Jiri Slaby
2020-07-24  6:27   ` Jiri Slaby
2020-07-24  6:27   ` Jiri Slaby
2020-07-24  7:58   ` Greg KH
2020-07-24  7:58     ` Greg KH
2020-07-24  7:58     ` Greg KH
2020-07-24  7:59     ` Jiri Slaby
2020-07-24  7:59       ` Jiri Slaby
2020-07-24  7:59       ` Jiri Slaby
2020-07-24  9:30   ` Sergei Shtylyov
2020-07-24  9:30     ` Sergei Shtylyov
2020-07-24  9:30     ` Sergei Shtylyov
2020-07-24  9:38     ` Greg KH
2020-07-24  9:38       ` Greg KH
2020-07-24  9:38       ` Greg KH
2020-07-24 10:30     ` Jiri Slaby [this message]
2020-07-24 10:30       ` Jiri Slaby
2020-07-24 10:30       ` Jiri Slaby

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=92c429c6-5cce-b5cc-877e-d4784651e31f@suse.cz \
    --to=jslaby@suse.cz \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=sergei.shtylyov@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.