On Fri, 17 May 2019 02:43:08 PDT (-0700), ktk...@virtuozzo.com wrote:
On 17.05.2019 12:41, Kirill Tkhai wrote:
On 17.05.2019 07:21, Stephen Rothwell wrote:
Hi all,
Please do not add any v5.3 material to your linux-next included
trees/branches until after v5.2-rc1 has been released.
Changes si
Hi all,
On Fri, 17 May 2019 12:43:08 +0300 Kirill Tkhai wrote:
>
> On 17.05.2019 12:41, Kirill Tkhai wrote:
> > On 17.05.2019 07:21, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Please do not add any v5.3 material to your linux-next included
> >> trees/branches until after v5.2-rc1 has been r
On 17.05.2019 12:41, Kirill Tkhai wrote:
> On 17.05.2019 07:21, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v5.3 material to your linux-next included
>> trees/branches until after v5.2-rc1 has been released.
>>
>> Changes since 20190516:
>>
>> The kvm tree gained conflicts agains
On 17.05.2019 07:21, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v5.3 material to your linux-next included
> trees/branches until after v5.2-rc1 has been released.
>
> Changes since 20190516:
>
> The kvm tree gained conflicts against Linus' tree.
>
> Non-merge commits (relative
On Fri, 17 May 2019 at 06:21, Stephen Rothwell wrote:
>
> Hi all,
>
> Please do not add any v5.3 material to your linux-next included
> trees/branches until after v5.2-rc1 has been released.
>
> Changes since 20190516:
>
> The kvm tree gained conflicts against Linus' tree.
When I built arm64 I sa
Hi all,
Please do not add any v5.3 material to your linux-next included
trees/branches until after v5.2-rc1 has been released.
Changes since 20190516:
The kvm tree gained conflicts against Linus' tree.
Non-merge commits (relative to Linus' tree): 1023
1119 files changed, 27058 insertions(+), 7
On Tue, May 22, 2018 at 03:18:43PM +0100, Mark Brown wrote:
> On Thu, May 17, 2018 at 05:06:56PM +1000, Stephen Rothwell wrote:
>
> > News: I will not be doing any linux-next releases between Friday 18 May
> > and Friday 25 May inclusive.
>
> Just noticed this, I'm going to try to cover starting
On Thu, May 17, 2018 at 05:06:56PM +1000, Stephen Rothwell wrote:
> News: I will not be doing any linux-next releases between Friday 18 May
> and Friday 25 May inclusive.
Just noticed this, I'm going to try to cover starting tomorrow. The
usual caveats about reduced service and reliability apply
On 05/17/2018 12:06 AM, Stephen Rothwell wrote:
> Hi all,
>
on x86_64:
drivers/pwm/pwm-stm32.o: In function `stm32_pwm_raw_capture':
pwm-stm32.c:(.text+0x53d): undefined reference to `stm32_timers_dma_burst_read'
when COMPILE_TEST=y and MFD_STM32_TIMERS is not set.
Any suggestions?
thanks,
-
On 17 May 2018 at 12:36, Stephen Rothwell wrote:
> Hi all,
>
> News: I will not be doing any linux-next releases between Friday 18 May
> and Friday 25 May inclusive.
>
> Changes since 20180516:
>
> New trees: devicetree-fixes
>
> The kbuild tree still had its build failure for which I applied a pa
On 05/17/2018 12:06 AM, Stephen Rothwell wrote:
>
> The usb-gadget tree gained a conflict against the usb tree.
>
on x86_64:
drivers/usb/gadget/udc/aspeed-vhub/hub.o: In function
`ast_vhub_std_hub_request':
hub.c:(.text+0x3a7): undefined reference to `usb_gadget_get_string'
CONFIG_LIB_USBCOM
Hi all,
News: I will not be doing any linux-next releases between Friday 18 May
and Friday 25 May inclusive.
Changes since 20180516:
New trees: devicetree-fixes
The kbuild tree still had its build failure for which I applied a patch.
The mvebu tree gained a conflict against the arm-soc tree.
Hi all,
Changes since 20170516:
New trees: nand-fixes (yesterday)
spi-nor-fixes
The file-locks tree gained a build failure so I used the version from
next-20170516.
The netfilter tree gained a build failure for which I applied a fix patch.
The sound tree gained a build failure so I use
Hi Stephen,
On Mon, May 23, 2016 at 4:37 PM, Stephen Rothwell wrote:
> Hi Xiong,
>
> On Mon, 23 May 2016 16:13:28 +0800 Xiong Zhou wrote:
>>
>> hi,
>>
>> On Tue, May 17, 2016 at 1:04 PM, Stephen Rothwell
>> wrote:
>> >
>> > I have created today's linux-next tree at
>> > git://git.kernel.org/pu
Hi Xiong,
On Mon, 23 May 2016 16:13:28 +0800 Xiong Zhou wrote:
>
> hi,
>
> On Tue, May 17, 2016 at 1:04 PM, Stephen Rothwell
> wrote:
> >
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > (patches at http://www.kernel.org/pu
hi,
On Tue, May 17, 2016 at 1:04 PM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v4.8 destined material to your linux-next included
> branches until after v4.7-rc1 has been released.
>
> Changes since 20160516:
>
> The vfs tree gained a conflict against the ext4 tree.
>
> The net-
Hi all,
Please do not add any v4.8 destined material to your linux-next included
branches until after v4.7-rc1 has been released.
Changes since 20160516:
The vfs tree gained a conflict against the ext4 tree.
The net-next tree gained a conflict against the arm64 tree.
The spi tree lost its buil
Hi all,
Changes since 20130516:
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you
are track
18 matches
Mail list logo
