Hi all,
Changes since 20190731:
New trees: pidfd-fixes, renesas-geert
My fixes tree contains:
15b9fc624ba4 ("drivers/macintosh/smu.c: Mark expected switch fall-through")
The pm tree lost its build failure.
The drm-misc tree gained a build failure so I used the version from
next-20190731.
T
On Thu, Aug 02, 2018 at 06:00:19AM -0700, Guenter Roeck wrote:
> Per my logs, next-20180730 is the first bad, next-20180727 is the last good.
OK, so my bisecting is correct (a bit too much but still).
--
Johannes Thumshirn Storage
jthumsh...@suse.de
On 08/01/2018 05:05 PM, Stephen Rothwell wrote:
Hi all,
On Wed, 01 Aug 2018 16:00:54 -0700 James Bottomley
wrote:
So what seems to be happening to cause this is that there's a patch
somewhere between the merge base of my scsi-next series and the next
tree and the patch just before scsi-next
On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180731:
>
> The pci tree gained a conflict against the pci-current tree.
>
> The net-next tree gained a conflict against the bpf tree.
>
> The block tree lost its build failure.
>
> The staging tree
Hi all,
Changes since 20180731:
The pci tree gained a conflict against the pci-current tree.
The net-next tree gained a conflict against the bpf tree.
The block tree lost its build failure.
The staging tree still had its build failure due to an interaction with
the vfs tree for which I disable
On Wed, Aug 2, 2017 at 1:55 AM, Sergey Senozhatsky
wrote:
> On (08/01/17 15:28), Arnd Bergmann wrote:
>> Does this fix it? I definitely got this part wrong as I see now, we must
>> look up the 'tail' after calling __tty_buffer_request_room, not before.
>
> yes, it does. thanks!
>
> Tested-by: Serg
Hello,
On (08/01/17 15:28), Arnd Bergmann wrote:
[..]
> > Looking into it now, sorry for the breakage.
>
> Does this fix it? I definitely got this part wrong as I see now, we must
> look up the 'tail' after calling __tty_buffer_request_room, not before.
yes, it does. thanks!
Tested-by: Sergey S
On Tue, Aug 1, 2017 at 3:20 PM, Arnd Bergmann wrote:
> On Tue, Aug 1, 2017 at 2:42 PM, Sergey Senozhatsky
> wrote:
>> Hello,
>>
>>
>> seems that commit 979990c6284814617 ("tty: improve tty_insert_flip_char()
>> fast path") panics my kernel.
>>
>> in particular, this part
>
> Looking into it now,
On Tue, Aug 1, 2017 at 2:42 PM, Sergey Senozhatsky
wrote:
> Hello,
>
>
> seems that commit 979990c6284814617 ("tty: improve tty_insert_flip_char()
> fast path") panics my kernel.
>
> in particular, this part
Looking into it now, sorry for the breakage.
Arnd
Hello,
seems that commit 979990c6284814617 ("tty: improve tty_insert_flip_char()
fast path") panics my kernel.
in particular, this part
@@ -26,7 +27,7 @@ static inline int tty_insert_flip_char(struct tty_port *port,
*char_buf_ptr(tb, tb->used++) = ch;
return 1;
Hi all,
Changes since 20170731:
The rdma tree lost its build failure.
I reverted a commit from the staging tree that was causing overnight
build failures.
The akpm-current tree gained a build failure for which I applied a patch
and another for which I reverted a commit.
The akpm tree gained a
Hi all,
Please do not add material destined for v4.9 to your linux-next included
branches until after v4.8-rc1 has been released.
Changes since 20160729:
New Tree: befs
Non-merge commits (relative to Linus' tree): 4300
3495 files changed, 145910 insertions(+), 65285 deletions(-)
-
Hi all,
Changes since 20140731:
The modules tree still had its build failure so I used the version from
next-20140725.
The mmc-uh tree still had its build failure so I used the version from
next-20140725.
The kvm tree gained a conflict against the ftrace tree.
The staging tree gained a conflic
On Thu, Aug 1, 2013 at 9:25 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130731:
>
> Removed trees: xen-arm (merged into the xen-tip tree)
>
> The ext4 tree still has its build failure so I used the version from
> next-20130726.
>
> The driver-core tree gained a conflict against the n
Hi all,
Changes since 20130731:
Removed trees: xen-arm (merged into the xen-tip tree)
The ext4 tree still has its build failure so I used the version from
next-20130726.
The driver-core tree gained a conflict against the net-next tree.
The usb-gadget tree lost its build failure but gained conf
15 matches
Mail list logo
