All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lafan Mining <lkfan@protonmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Greg KH <greg@kroah.com>,
	"kernelnewbies@kernelnewbies.org"
	<kernelnewbies@kernelnewbies.org>
Subject: Re: Kernel upstream compile error at drivers/staging/media
Date: Fri, 10 Sep 2021 10:31:45 +0000	[thread overview]
Message-ID: <IKHOSvAlC3X8UV5pNj4doeEQGnFAFp9VT25ATHQo1LOl8gWxrlyod6gX7aX86RYQDwmj8FiyhPQ8TJlR3CdXnVGOQWWI3EiUCRajQeU8smg=@protonmail.com> (raw)
In-Reply-To: <CAKXUXMyob=ifw866WTFPUf7R4JUGFqCA4vnv+=o2qDHTUQZkJg@mail.gmail.com>

On Wednesday, September 8th, 2021 at 7:19 PM, Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:

> integration tree, and hence in linux-next

So generally to get the latest kernel version that is going to be merged into master soon is using linux-next's master? I looked at the https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/staging/media/atomisp/pci/hive_isp_css_common/host/input_system.c and it was indeed fixed.

Thanks.

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

  reply	other threads:[~2021-09-10 10:33 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
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 [this message]
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='IKHOSvAlC3X8UV5pNj4doeEQGnFAFp9VT25ATHQo1LOl8gWxrlyod6gX7aX86RYQDwmj8FiyhPQ8TJlR3CdXnVGOQWWI3EiUCRajQeU8smg=@protonmail.com' \
    --to=lkfan@protonmail.com \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=lukas.bulwahn@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.