All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Lafan Mining <lkfan@protonmail.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Kernel upstream compile error at drivers/staging/media
Date: Wed, 8 Sep 2021 12:06:46 +0200	[thread overview]
Message-ID: <YTiLNoR7hswTDs4W@kroah.com> (raw)
In-Reply-To: <xnLYp2w2NB-PcNzq7IBilAYBJQdzTPe3vBF24xBHpmDkZBSSXtMir4sHm7nenGEn6fgt6gjB-CaL_xnIGFJjoJV5kOuGgU9Z12qPbGQKtP8=@protonmail.com>

On Wed, Sep 08, 2021 at 10:02:50AM +0000, Lafan Mining wrote:
> On Wednesday, September 8th, 2021 at 12:50 PM, Greg KH <greg@kroah.com> wrote:
> 
> > Please update your kernel version, this should already be fixed.
> >
> > What version exactly are you trying to build?
> 
> I tried to build the latest source code available in master. Judging by the latest tag name it's v5.14-rc7.

That is quite old, 5.14 was released on August 29, and there have been
9718 changes added to the tree since then.

> When pulling for new changes with git pull there was "Already up to date" message.

What exactly is the tree you are pulling from?

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-09-08 10:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  9:39 Kernel upstream compile error at drivers/staging/media Lafan Mining
2021-09-08  9:50 ` Greg KH
2021-09-08 10:02   ` Lafan Mining
2021-09-08 10:06     ` Greg KH [this message]
2021-09-08 10:36       ` Lafan Mining
2021-09-08 15:59   ` Lafan Mining
2021-09-08 16:19     ` Lukas Bulwahn
2021-09-10 10:31       ` Lafan Mining
2021-09-10 10:52         ` Lukas Bulwahn

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=YTiLNoR7hswTDs4W@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=lkfan@protonmail.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.