From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/v4l2loopback: bump to version 0b8feb80fdef9a415d8250bca1790b3ff23e8391
Date: Sun, 26 May 2019 21:33:18 +0200 [thread overview]
Message-ID: <20190526213318.3e54c484@windsurf> (raw)
In-Reply-To: <CADvTj4rh8At+7G-nt0uO1VSyYqkLt35npGi1smWrYOJ296XwDw@mail.gmail.com>
Hello James,
On Fri, 24 May 2019 15:40:33 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> > Could you comment on what are the other commits between v0.12.1 and
> > 0b8feb80fdef9a415d8250bca1790b3ff23e8391 ? Only bug fixes, and we
> > should take all of them to master ? Or should we just backport the
> > Linux 5.1 fix ?
> Other than a readme change there are no commits between v0.12.1 and
> 0b8feb80fdef9a415d8250bca1790b3ff23e8391.
I think in this case, it makes more sense to just "backport" the single
patch that fixes this issue, and put it in package/v4l2loopback/. Could
you send an updated version of your patch with this solution instead ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-26 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 20:35 [Buildroot] [PATCH 1/1] package/v4l2loopback: bump to version 0b8feb80fdef9a415d8250bca1790b3ff23e8391 James Hilliard
2019-05-24 21:13 ` Thomas Petazzoni
2019-05-24 21:16 ` James Hilliard
2019-05-24 21:24 ` Thomas Petazzoni
2019-05-24 21:40 ` James Hilliard
2019-05-26 19:33 ` Thomas Petazzoni [this message]
2019-05-27 18:52 ` James Hilliard
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=20190526213318.3e54c484@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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