merged
Bruce
On Thu, Aug 29, 2019 at 3:08 AM Xulin Sun wrote:
>
> This adds the cfg & scc files to support the LS2088A-RDB.
>
> Signed-off-by: Xulin Sun
> ---
> bsp/nxp-ls20xx/nxp-ls20xx-standard.scc | 8 ++
> bsp/nxp-ls20xx/nxp-ls20xx.cfg | 162 +
>
all three are now merged to linux-yocto-dev.
Bruce
On Thu, Aug 29, 2019 at 2:31 AM wrote:
>
> From: Limeng
>
> Hi Bruce,
>
> I am working on BSP renesas-rcar platform, and intend to merge this BSP
> supporting into yocto community.
> Below 3 patches are used to improve gpio, CAN BUS, audio
merged to master.
Bruce
On Tue, Aug 27, 2019 at 4:59 AM wrote:
>
> From: Limeng
>
> On KingFisher board, there is PCM3168A codec chip, so enable
> PCM3168A-I2C codec driver by setting configure
> CONFIG_SND_SOC_PCM3168A_I2C
>
> Signed-off-by: Meng Li
> ---
> bsp/renesas-rcar/renesas-rcar.cfg
merged
Bruce
On Thu, Aug 29, 2019 at 9:52 AM wrote:
>
> From: "J. R. Okajima"
>
> Simply follows the commit in mainline,
> 622445541b75 2019-07-29 kbuild: detect missing "WITH
> Linux-syscall-note" for uapi headers
>
> Signed-off-by: J. R. Okajima
>
> Backport from
oops. Sorry about that, I forgot to push the resolution I did earlier
today for this. It should be in the tree now.
Bruce
On Mon, Aug 26, 2019 at 10:14 PM wrote:
>
> From: He Zhe
>
> This is the missing half of the following commit that is cracked during
> merging,
> which causes build
Hmm. That wasn't on purpose. My builds ran overnight, so I'll have a
look and fix it up.
Bruce
>
> --
>
> commit b73b90b1d2cc6b4ba740e66479ab054482174f94
> Merge: ce4ec6f a55aa89
> Author: Bruce Ashfield
&g
On Wed, Aug 21, 2019 at 6:15 AM wrote:
>
> From: Limeng
>
> Hi Bruce,
>
> I am working on BSP renesas-rcar platform, and intend to merge this BSP
> supporting into yocto community.
> Below patch includes scc and cfg files for renesas-rcar platform.
>
> Could you please merge this patch into
On Sun, Aug 18, 2019 at 10:14 AM Paul Gortmaker
wrote:
>
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.41 release.
>
> There are about 150 commits here, based on the remaining
On Fri, Aug 16, 2019 at 12:01 PM wrote:
>
>
> 在 2019年8月16日 23:29，Paul Gortmaker 写下:
> >
> > [[linux-yocto] [PATCH] modules: always page-align module section
> > allocations] On 16/08/2019 (Fri 15:36) zhe...@windriver.com wrote:
> >
> > It helps maintainers if the version is embedded in the
merged
Bruce
On Thu, Aug 15, 2019 at 5:29 AM Jun Miao wrote:
>
> add Power Management IC support.
> TPS65910: am335x EVM/SK
> TPS65217: am335x BBB
>
> Signed-off-by: Jun Miao
> ---
> bsp/ti-am335x/ti-am335x.cfg | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git
I've merged these to the 4.19/5.0/5.2 and master branches.
SRCREV updates will follow this week, once I get some more test cycles
completed.
Bruce
On Sun, Aug 11, 2019 at 12:29 PM Armin Kuster wrote:
> It is time to move the kernel fragments out of meta-security to cache.
> It should make
uce
>
>1 # for oprofile and powertop
>2 CONFIG_PROFILING=y
>3 CONFIG_OPROFILE=y
>4 CONFIG_FRAME_POINTER=y
>5 CONFIG_X86_LOCAL_APIC=y
>
> Maybe split profiling.cfg and move them to their recipe is a good way.
>
>
> --Hongzhi
>
>
>
>
On Fri, Aug 2, 2019 at 11:43 PM Paul Gortmaker
wrote:
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.40 release.
>
> There are about 220 commits here, based on commits chosen from
I've merged v2, and created the standard/ti-am335x in linux-yocto-dev.
Bruce
On Wed, Aug 7, 2019 at 3:54 AM Jun Miao wrote:
> Add scc/cfg kernel fragment to build and boot EVM/SK and BeagleBone Black
> boards all with am335x soc
>
> Signed-off-by: Jun Miao
> ---
>
On Wed, Aug 7, 2019 at 2:01 AM Jun Miao wrote:
>
> On 8/7/19 10:45 AM, Bruce Ashfield wrote:
> > On Tue, Aug 6, 2019 at 6:20 AM Jun Miao wrote:
> >
> >> Hi Bruce,
> >>
> >> I am working ti boards(AM335x evm/sk/BBB) with am335x soc.
> &g
I'm not sure if the intel folks are using these fragments and object to the
different behaviour, but they look ok to me. I've merged them for now, but
will reconsider if they cause problems in other configs.
Bruce
On Wed, Aug 7, 2019 at 3:27 AM Yongxin Liu
wrote:
> This config specifies the
On Wed, Aug 7, 2019 at 3:25 AM wrote:
> From: He Zhe
>
> Remove nfsd patch from nfsd-enable.scc which can be included directly or by
> other features, and thus cause re-application of the patch.
>
> Create nfs.scc to include both configuration and patches for potential
> inclusion
> for BSPs
Looks fine to me.
I'm traveling right now, so it will be a few days until I get this merged
and can send SRCREV updates to oe-core.
Bruce
On Tue, Aug 6, 2019 at 3:06 PM William Bourque wrote:
> Kconfiglib/* were under ISC license before they were imported
> here from
On Tue, Aug 6, 2019 at 6:49 AM wrote:
> From: He Zhe
>
> reply_cache_stats uses wrong parameter as seq file private structure and
> thus causes the following kernel crash when users read
> /proc/fs/nfsd/reply_cache_stats
>
> BUG: kernel NULL pointer dereference, address: 01f9
> PGD
On Tue, Aug 6, 2019 at 6:20 AM Jun Miao wrote:
> Add scc/cfg kernel fragment to build and boot EVM/SK and BeagleBone Black
> boards all with am335x soc
>
> Signed-off-by: Jun Miao
> ---
> bsp/ti-am335x/ti-am335x-standard.scc | 8 +
> bsp/ti-am335x/ti-am335x.cfg | 242
On Tue, Aug 6, 2019 at 6:20 AM Jun Miao wrote:
> Hi Bruce,
>
> I am working ti boards(AM335x evm/sk/BBB) with am335x soc.
>
> 1.This patch add scc/cfg to yocto-kernel-cache master branch.
>
#1 shouldn't be a problem.
2.Could you help me build a new branch "ti-am335x" in
On Mon, Aug 5, 2019 at 11:44 PM Hongzhi, Song
wrote:
> Hi Bruce,
>
> I see profiling.scc is included by kernel-cache/bsp/*, such as
> bsp/intel-x86 bsp/common-pc/ ... .
>
>
> My question is that is it necessary to open profiling.cfg defaultly?
>
We left profiling as a per-BSP decision, since
, Jul 30, 2019 at 10:12 AM Bruce Ashfield
wrote:
> See the email on the poky/oe-core list. I was having some issues with 5.3
> and the new libc-headers. So I wasn't able to send the PV bump patch for
> linux-yocto. I've temporarily gone back to a building configuration, but I
> expect th
See the email on the poky/oe-core list. I was having some issues with 5.3
and the new libc-headers. So I wasn't able to send the PV bump patch for
linux-yocto. I've temporarily gone back to a building configuration, but I
expect that I'll have it back to 5.3 in the next day or so.
Bruce
On Tue,
On Thu, Jul 25, 2019 at 9:43 PM He Zhe wrote:
>
>
> On 7/25/19 9:04 PM, Bruce Ashfield wrote:
> > On Thu, Jul 25, 2019 at 9:03 AM Bruce Ashfield
> wrote:
> >> On Thu, Jul 25, 2019 at 4:54 AM wrote:
> >>> From: YueHaibing
> >>>
>
It is now merged.
Bruce
On Wed, Jul 24, 2019 at 10:25 AM qwang2 wrote:
>
> Hi Bruce,
>
> Could this patch be merged to linux-yocto-dev now?
>
> Thanks,
>
> Quanyang
>
> On 2019/7/23 上午11:11, quanyang.w...@windriver.com wrote:
> > From: Quanyang Wang
> >
> > Hi Bruce,
> >
> > Would you please
On Thu, Jul 25, 2019 at 9:03 AM Bruce Ashfield wrote:
>
> On Thu, Jul 25, 2019 at 4:54 AM wrote:
> >
> > From: YueHaibing
> >
> > If CONFIG_BTRFS_FS is y and CONFIG_LIBCRC32C is m,
> > building fails:
>
> I've already fixed this by changing the configu
On Thu, Jul 25, 2019 at 4:54 AM wrote:
>
> From: YueHaibing
>
> If CONFIG_BTRFS_FS is y and CONFIG_LIBCRC32C is m,
> building fails:
I've already fixed this by changing the configuration in the kernel-cache. I'll
pick this up in linux-yocto-dev once it makes a -rc release.
Bruce
>
>
On Tue, Jul 23, 2019 at 9:20 AM Yunguo Wei wrote:
>
>
>
> 在 2019/7/23 21:03, qwang2 写道:
> >
> > On 7/23/19 8:41 PM, Bruce Ashfield wrote:
> >> On Tue, Jul 23, 2019 at 1:29 AM qwang2
> >> wrote:
> >>>
> >>> On 7/22/19 11:34 PM, B
On Tue, Jul 23, 2019 at 1:29 AM qwang2 wrote:
>
>
> On 7/22/19 11:34 PM, Bruce Ashfield wrote:
> > On Mon, Jul 22, 2019 at 1:24 AM wrote:
> >> From: Quanyang Wang
> >>
> >> Hi Bruce,
> >>
> >> Would you please help merge these
merged to master and yocto-5.2 branches.
Bruce
On Mon, Jul 22, 2019 at 7:35 AM wrote:
>
> From: Quanyang Wang
>
> Hi Bruce,
>
> Would you please help to merge this patch to yocto-kernel-cache master?
>
> --LOG
> Booting Linux on physical CPU 0x00 [0x410fd034]
>
On Mon, Jul 22, 2019 at 1:24 AM wrote:
>
> From: Quanyang Wang
>
> Hi Bruce,
>
> Would you please help merge these 2 patches to linux-yocto-dev
> standard/xlnx-soc branch?
I've merged the patches.
Also note: I'm about to move linux-yocto-dev to v5.3-rc1, so I've
created a set of v5.2 branches
On Tue, Jul 16, 2019 at 3:01 AM Anuj Mittal wrote:
>
> Hi Bruce,
>
> Could you merge in 4.19, 5.0 and master if these look okay? Thank you.
>
They look fine to me, and are now on those three branches.
Bruce
> Anuj Mittal (3):
> security.cfg: unset HARDENED_USERCOPY_FALLBACK
> features: add
On Thu, Jul 18, 2019 at 9:36 AM Bruce Ashfield wrote:
>
> On Thu, Jul 18, 2019 at 8:30 AM Michal Simek wrote:
> >
> > On 16. 07. 19 21:44, Bruce Ashfield wrote:
> > > On Mon, Jul 15, 2019 at 2:19 AM Wei, Yunguo
> > > wrote:
> > >>
> &g
On Thu, Jul 18, 2019 at 8:30 AM Michal Simek wrote:
>
> On 16. 07. 19 21:44, Bruce Ashfield wrote:
> > On Mon, Jul 15, 2019 at 2:19 AM Wei, Yunguo
> > wrote:
> >>
> >>
> >> On 7/8/2019 9:14 PM, Bruce Ashfield wrote:
> >>> On Thu,
I was doing some cleanup before the
push.
Sorry for the delay, but it is now really merged.
Bruce
>
> Thanks,
> Yongxin
>
> > -Original Message-
> > From: Liu, Yongxin
> > Sent: Thursday, July 11, 2019 18:49
> > To: 'Bruce Ashfield'
> >
On Wed, Jul 17, 2019 at 7:43 AM praveen vattipalli
wrote:
>
> Hi All,
> we are upgrading Yocto from Krogath to Sumo version.
> while using meta-altera kernel source as local source,
>
> if i use EXTERNALSRC_BUILD variable
> EXTERNALSRC =
>
merged
Bruce
On Tue, Jul 9, 2019 at 3:51 AM Yongxin Liu wrote:
>
> Because CONFIG_DEV_DAX* are not supported in preempt-rt kernel, use
> two scc files for Non-RT kerel and RT kernel separately.
>
> Signed-off-by: Yongxin Liu
> ---
> .../intel-persistent-memory/intel-x86-64-dax.cfg | 7
merged
Bruce
On Mon, Jul 8, 2019 at 4:24 AM Liwei Song wrote:
>
> Enable CONFIG_DRM_MGAG200=m to support Matrox Electronics MGA G200
> and include it in intel-x86 bsp.
>
> Signed-off-by: Liwei Song
> ---
> bsp/intel-x86/intel-x86.scc | 1 +
> features/mgag200/mgag200.cfg | 1 +
>
On Wed, Jul 3, 2019 at 10:54 AM wrote:
>
> From: He Zhe
>
> Since b5776165c9d3 ("netfilter: Fix remainder of pseudo-header protocol 0"),
> net.scc includes a patch which would be reapplied when included by other
> features.
>
> This patches create a config variant net-enable.scc for features and
t;
> git://github.com/justanotherboy/yocto-kernel-cache yocto-4.19-scsi
> https://github.com/justanotherboy/yocto-kernel-cache/tree/yocto-4.19-scsi
>
> Bruce Ashfield (1):
> scsi-debug: include core scsi support for standalone inclusion
>
> features/s
merged.
Bruce
On Sun, Jun 30, 2019 at 10:09 PM wrote:
>
> From: Mingli Yu
>
> As nss-pam-ldapd depends on libpam, it should do
> required distro feature check for pam.
>
> Signed-off-by: Mingli Yu
> ---
> recipes-support/nss-pam-ldapd/nss-pam-ldapd_0.9.8.bb | 3 ++-
> 1 file changed, 2
merged
Bruce
On Sun, Jun 30, 2019 at 10:08 PM wrote:
>
> From: Mingli Yu
>
> Since spice of meta-cloud-services depends on
> cyrus-sasl which comes from networking-layer,
> add missing layer depends back.
>
> Signed-off-by: Mingli Yu
> ---
> conf/layer.conf | 2 +-
> 1 file changed, 1
On Tue, Jul 2, 2019 at 12:17 PM He Zhe wrote:
>
>
>
> On 7/2/19 9:16 PM, He Zhe wrote:
> >
> > On 7/2/19 9:04 PM, Bruce Ashfield wrote:
> >> On Tue, Jul 2, 2019 at 4:54 AM wrote:
> >>> From: He Zhe
> >>>
> >>> The pa
mistakenly
> -treated as TCP/UDP.
> -
> -This patch corrects the conditions in nf_ip_checksum and all other places
> that
> -still call it with protocol 0.
> -
> -Fixes: 7fc38225363d ("netfilter: reject: skip csum verification for
> protocols that don't support it")
&
On Wed, Jun 26, 2019 at 11:02 PM wrote:
>
> From: He Zhe
>
> Signed-off-by: He Zhe
> ---
> v2: Add a note for people using uvesafb or other similar things.
>
merged.
Bruce
> features/security/security.cfg | 18 ++
> 1 file changed, 18 insertions(+)
>
> diff --git
On Tue, Jun 25, 2019 at 11:03 PM He Zhe wrote:
>
>
>
> On 6/26/19 11:00 AM, Bruce Ashfield wrote:
> > On Tue, Jun 25, 2019 at 6:15 AM wrote:
> >> From: He Zhe
> >>
> >> Since v5.1-rc1, some types of packets do not get unreachable reply with the
On Tue, Jun 25, 2019 at 10:55 PM He Zhe wrote:
>
>
>
> On 6/26/19 10:49 AM, Bruce Ashfield wrote:
> > On Tue, Jun 25, 2019 at 10:25 AM He Zhe wrote:
> >> Hi Bruce,
> >>
> >> Have you ever met the following error with features/security/security.sc
On Tue, Jun 25, 2019 at 11:00 PM Bruce Ashfield
wrote:
>
> On Tue, Jun 25, 2019 at 6:15 AM wrote:
> >
> > From: He Zhe
> >
> > Since v5.1-rc1, some types of packets do not get unreachable reply with the
> > following iptables setting. Fox example,
>
>
On Tue, Jun 25, 2019 at 6:15 AM wrote:
>
> From: He Zhe
>
> Since v5.1-rc1, some types of packets do not get unreachable reply with the
> following iptables setting. Fox example,
So what's the upstream status of this ? (I haven't checked netdev yet).
Bruce
>
> $ iptables -A INPUT -p icmp
On Tue, Jun 25, 2019 at 10:25 AM He Zhe wrote:
>
> Hi Bruce,
>
> Have you ever met the following error with features/security/security.scc,
> when running qemux86?
Hmm. No, I haven't seen that.
My old builds were using sysvinit, so I didn't have a recent build
ready to go. But I just started a
On Sun, Jun 16, 2019 at 11:45 AM Adrian Freihofer
wrote:
>
> Hi, Bruce,
>
> Compared to v1, this is more or less a rewrite. It is now very similar to the
> qemuarma15 BSP as suggested by you.
>
> The qemuarm15 BSP generates a kernel of 7046128 bytes.
> The current Beaglebone yocto configuration
Sorry for the delay.
I was out of the office for a bit, and I'm having a look at this now.
Bruce
On Sun, Jun 16, 2019 at 11:45 AM Adrian Freihofer
wrote:
>
> Hi, Bruce,
>
> Compared to v1, this is more or less a rewrite. It is now very similar to the
> qemuarma15 BSP as suggested by you.
>
>
I had queued -rc6 this morning .. and then noticed this.
I've pushed the changes, so we are covered, now that the -dev kernel is updated.
Bruce
On Mon, Jun 24, 2019 at 5:39 AM wrote:
>
> From: Miklos Szeredi
>
> This reverts commit d4b13963f217dd947da5c0cabd1569e914d21699.
>
> The commit
thanks~
>
> git://git.yoctoproject.org/linux-yocto-dev
>
>
> Cheers,
>
> Zumeng
>
> On 6/11/19 7:37 AM, Zumeng Chen wrote:
>
>
> On 6/10/19 9:37 PM, Bruce Ashfield wrote:
>
> On Sun, Jun 9, 2019 at 8:00 PM Zumeng Chen wrote:
>
> Sounds I like mean, no,
On Sun, Jun 9, 2019 at 8:00 PM Zumeng Chen wrote:
>
> Sounds I like mean, no, I just talk the reality, Xilinx did like the
> following:
>
> https://github.com/Xilinx/meta-xilinx/tree/master/meta-xilinx-bsp/recipes-kernel/linux/xilinx-kmeta/bsp
>
> I think they have a reason to share zynq-7000
On Sun, Jun 9, 2019 at 8:49 AM Adrian Freihofer
wrote:
>
> Purpose: Provide an easy way to add ARCH_VIRT=y to the kernel configuration.
> This allows to boot ARM images compiled for real hardware in Qemu as well.
> Including this feature e.g. into the Beaglebone BSP allows to:
We already have
On Sun, Jun 9, 2019 at 8:49 AM Adrian Freihofer
wrote:
>
> The purpose/idea is documented here:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13384
Just cut and paste the reasons into the cover letter + patches. Not
all reviews are done online
and having the info quickly available for git
as perhaps being selected by an
option, or a default configuration was being assumed .. you will see
some minor deltas.
Bruce
>
> Pierluigi
>
> On 06/06/19 15:47, Bruce Ashfield wrote:
> > On Thu, Jun 6, 2019 at 9:38 AM Pierluigi Greto
> > wrote:
> >> Hi,
> >>
On Thu, Jun 6, 2019 at 9:38 AM Pierluigi Greto wrote:
>
> Hi,
>
> I have to create a custom 4.14.49 linux kernel. In my recipe I have added my
> defconfig, but yocto it's not taking in consideration the defconfig. Instead
> it's building the kernel using the default values. Also the compilation
On Wed, Jun 5, 2019 at 4:02 AM Zumeng Chen wrote:
>
> This patch is to add scc/cfg meta to build and boot zcu102 board with the bsp
> of xilinx-zynqmp.
>
See some questions below.
> Signed-off-by: Zumeng.Chen
> ---
> bsp/xilinx-zynqmp/xilinx-zynqmp-standard.scc | 8 +
>
On Wed, Jun 5, 2019 at 4:08 AM Zumeng Chen wrote:
>
> Hi Bruce,
>
> Forget this party :)
>
>
> xilinx-zynqmp is arm64 BSP with cortexA53, and it seems stable in mainline
> to build and boot, so I add it into linux-yocto-dev and yocto-kernel-cache.
> This email is just about scc/cfg, no extra
merged, and SRCREV bumps sent to the oe-core list.
Bruce
On Sat, Jun 1, 2019 at 6:32 PM Mariano López
wrote:
>
> Hi Bruce,
>
> This will add the configuration options to enable the SCSI debug module
> that is needed by the util-linux ptest package. This is needed to add
> KERNEL_FEATURES in the
Thanks Paul, this is now merged.
Bruce
On Thu, May 30, 2019 at 10:24 PM Paul Gortmaker
wrote:
>
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.39 release.
>
> There are about 260
On Thu, May 30, 2019 at 8:37 AM Belisko Marek wrote:
>
> On Thu, May 30, 2019 at 2:35 PM Bruce Ashfield
> wrote:
> >
> > On Thu, May 30, 2019 at 4:14 AM Belisko Marek
> > wrote:
> > >
> > > Hi,
> > >
> > > I'm trying to add
On Thu, May 30, 2019 at 4:14 AM Belisko Marek wrote:
>
> Hi,
>
> I'm trying to add support for latest possible released kernel in
> meta-sunxi by using poky warrior and hit this QA issue:
> ERROR: linux-mainline-5.2-rc2-r0 do_package: QA Issue: linux-mainline:
> Files/directories were installed
I've refreshed all the 5.0 -rt versions, so this no longer applies.
Can you check the latest changes on the branches and re-send if this
is still required.
Bruce
On Tue, May 28, 2019 at 11:56 PM Liwei Song wrote:
>
> From: Jiping Ma
>
> Use a local_irq_lock as a replacement for irq off
On Thu, May 23, 2019 at 11:09 PM Paul Gortmaker
wrote:
>
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.38 release.
>
> There are about 180 commits here, based on commits chosen from
I'm doing full updates on the 5.0 -rt at the moment, so I'll pickup
this fix along with the reset of the recent -rt changes upstream.
Bruce
On Thu, May 23, 2019 at 5:55 AM Liwei Song wrote:
>
> fix following compile error:
>
> kernel/irq/manage.c:388:20: error: passing argument 1 of
On Fri, May 24, 2019 at 12:27 PM Mauro Ziliani wrote:
>
> Hi all.
>
> How can I ask to bitbake which is the actual value of virtual/kernel?
>
Here's one way:
bitbake -e virtual/kernel | grep PREFERRED_PROVIDER_virtual\/kernel
# $PREFERRED_PROVIDER_virtual/kernel [2 operations]
On Fri, May 24, 2019 at 8:50 AM Bruce Ashfield
wrote:
>
>
> On Fri, May 24, 2019 at 7:24 AM Zoran Stojsavljevic <
> zoran.stojsavlje...@gmail.com> wrote:
>
>> As I said, I am a man of experimental try-outs. And here is the try!
>>
>> Now, after setting
systemtap \
>> > > "
>> > >
>> > > Problem with this approach is that such a kernel makes the
>> rootfs too
>> > > big and impractical:
>> > > -rw-r--r--. 2 user vboxusers 101499952 May 17 14:32
>> > >
l.
I'm going to create two new optional packages for the fall release that are
simply captured kernel-source and kernel-headers for those uses cases where
someone really does want the entire source tree, or just the headers. The
details for that work are in bugzilla.
Bruce
>
> >
&g
On Thu, May 23, 2019 at 12:20 PM Andrei Gherzan wrote:
>
> On 23/05/2019 17.11, Bruce Ashfield wrote:
>
>
>
> On Thu, May 23, 2019 at 11:24 AM Andrei Gherzan wrote:
>
>> On 23/05/2019 16.10, Bruce Ashfield wrote:
>>
>>
>>
>> On Thu
On Thu, May 23, 2019 at 11:24 AM Andrei Gherzan wrote:
> On 23/05/2019 16.10, Bruce Ashfield wrote:
>
>
>
> On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan wrote:
>
>>
>> On 23/05/2019 15.39, Bruce Ashfield wrote:
>>
>>
>>
>> On
On Thu, May 23, 2019 at 11:00 AM Andrei Gherzan wrote:
>
> On 23/05/2019 15.39, Bruce Ashfield wrote:
>
>
>
> On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield
> wrote:
>
>>
>>
>> On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote:
>>
>>>
On Thu, May 23, 2019 at 10:39 AM Andrei Gherzan wrote:
> On 23/05/2019 15.32, Bruce Ashfield wrote:
>
>
>
> On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote:
>
>> Hello,
>>
>> This might have been discussed before. I couldn't find a relevant
>
On Thu, May 23, 2019 at 10:32 AM Bruce Ashfield
wrote:
>
>
> On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote:
>
>> Hello,
>>
>> This might have been discussed before. I couldn't find a relevant
>> thread, but if it is so, just link me to it.
&
On Thu, May 23, 2019 at 9:56 AM Andrei Gherzan wrote:
> Hello,
>
> This might have been discussed before. I couldn't find a relevant
> thread, but if it is so, just link me to it.
>
> Since thud, more specific since
>
> commit 9af0f1a46bbb6ad9ee8b35957251f4aa826b023f
g said, they are optional. I might be misreading, but what exactly
are you trying to build that requires that specific structure ? We are both
rebuilding the entire kernel and out of tree modules all the time with the
existing structure/path of the on-target installs.
kernel-devsrc itself is a
merged.
Bruce
On Sat, May 18, 2019 at 11:32 AM Hongxu Jia
wrote:
> Since commit [70a44a0 genirq: Prevent use-after-free and work list
> corruption] applied, the patch makes it work on rt
>
> Signed-off-by: Hongxu Jia
> ---
> kernel/irq/manage.c | 4
> 1 file changed, 4 insertions(+)
>
>
On Sun, May 19, 2019 at 10:51 AM Paul Gortmaker <
paul.gortma...@windriver.com> wrote:
> [Re: v4.18.x - stable updates comprising v4.18.38] On 16/05/2019 (Thu
> 16:47) Paul Gortmaker wrote:
>
> [...]
>
> > > The conflicts just look like one of the changes is already in my tree
> .. which
> > >
On Wed, May 15, 2019 at 6:07 PM Paul Gortmaker
wrote:
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.37 release.
>
> There is one trivial one line commit to fix a build error on
Both are now merged to master.
Bruce
On Wed, May 15, 2019 at 10:32 PM Mittal, Anuj wrote:
> Hi Bruce,
>
> Both these changes are only for master and are specific to v5.1.
>
> On Thu, 2019-05-16 at 10:26 +0800, Anuj Mittal wrote:
> > This has been removed starting v5.1 and nf_nat_ipv4,6 have
merged.
Bruce
On Tue, May 14, 2019 at 10:33 AM Daniel Dragomir <
daniel.drago...@windriver.com> wrote:
> Disabled correctable errors reporting for SYSMEM and CMEM by default.
>
> EDAC_AXXIA_SYSMEM_SKIP_CORRECTABLE:
> Support for deactivation of processing of SYSMEM correctable errors
> (single
merged.
SRCREV updates will follow with my next round of -stable bumps.
Bruce
On Tue, May 14, 2019 at 5:09 AM Liwei Song wrote:
> From: Takashi Iwai
>
> commit f495222e28275222ab6fd93813bd3d462e16d340 upstream.
>
> Currently the IRQ handler in HD-audio controller driver is registered
>
On Tue, May 14, 2019 at 9:18 AM Daniel Dragomir <
daniel.drago...@windriver.com> wrote:
> Hello Bruce!
>
> I know 4.1 is not supported anymore, but if possible,
> please review and merge this series of patches in
>
I'm still doing -stable updates when I can to 4.1 (I'm a bit behind at the
not going to it first.
Hopefully I'll get some new patches out in the coming month before summer
holidays really kick in.
Bruce
> Just thinking loud...
>
> Zoran
> ___
>
> On Wed, May 15, 2019 at 4:25 PM Bruce Ashfield
> wrote:
> >
> >
> >
>
IIRC the autobuilders
are using a sato based image (Richard could confirm more easily that I
could what image type the autobuilders are using for hello-world on target
module tests).
Bruce
>
> Thank you,
> Zoran
> ___
>
>
> On Wed, May 15, 2019 at 7:41 AM Bruce
On Tue, May 14, 2019 at 1:30 PM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> Hello Chris, Bruce,
>
> I have some additional data to share with you both, since I have tried
> something. And here is my take on the things!
>
> > 1. Build using a bb recipe.
> > Take a look at
On Sun, May 12, 2019 at 6:54 AM Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> Hello to the YOCTO community,
>
> I am using (to build the target for Beagle Bone Black) the following
> script:
> https://github.com/ZoranStojsavljevic/bbb-yocto
>
On Fri, May 10, 2019 at 4:32 AM wrote:
> From: Liu Haitao
>
> The following call trace would be triggered as kmemleak is running.
>
> BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:974
> in_atomic(): 1, irqs_disabled(): 1, pid: 2401, name: kmemleak
> Preemption
tojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/target-bbb-platform-traces.txt
>
>
While interesting .. it really isn't relevant in this context. But thanks
for sharing anyway!
Cheers,
Bruce
> Thank you,
> Zoran
> ___
>
> On Thu, May 9, 2019 at 2:53 PM Bruce Ash
On Thu, May 9, 2019 at 8:10 AM Kevin Hao wrote:
> Boot test for all these boards.
>
>
I do have more -stable updates coming, and you are seeing some queued 5.0.x
changes that I haven't sent yet (since I'm hung up on resolving a 4.19
conflict for one of the SoC branches), but yes, the changes
On Mon, May 6, 2019 at 9:45 PM Liwei Song wrote:
>
>
> On 05/07/2019 03:51 AM, Bruce Ashfield wrote:
> > I was just checking the mainline patch queues and didn't see an obvious
> > variant of this change. Are you seeing something upstream (submitted by
> > Takashi) ?
&
On Mon, May 6, 2019 at 11:41 AM Paul Gortmaker
wrote:
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.35 release.
>
> There are just over 185 commits here, based on commits chosen
I was just checking the mainline patch queues and didn't see an obvious
variant of this change. Are you seeing something upstream (submitted by
Takashi) ?
Bruce
On Mon, Apr 29, 2019 at 11:38 PM Liwei Song
wrote:
>
>
> On 04/30/2019 03:38 AM, Bruce Ashfield wrote:
> > On Sun, Ap
On Sat, May 4, 2019 at 10:07 AM Emily Smith wrote:
> Hi Randy -
>
> Good point it might be. Should I ask the meta-Xilinx maintainers about
> getting it in there?
>
>
That's probably the right thing to do, and/or just ask on the xilinx
mailing list what the plans are for releasing the code in a
merged to all branches.
Bruce
On Sun, Apr 28, 2019 at 6:53 AM He Zhe wrote:
> This is for all branches from 4.19 to 5.0.
>
> Zhe
>
> On 4/28/19 6:52 PM, zhe...@windriver.com wrote:
> > From: He Zhe
> >
> > b470fb994ebd ("tracing/x86: Save CR2 before tracing irqsoff on
> error_entry")
> >
On Sun, Apr 28, 2019 at 4:42 AM Liwei Song wrote:
> Fix the following BUG:
>
>
Is this also a bug in the mainline kernel ? If so, what's the resolution
for the issue there ?
Bruce
> BUG: unable to handle kernel NULL pointer dereference at 000c
> Workqueue: events azx_probe_work
101 - 200 of 2361 matches
Mail list logo
