On 2/23/21 7:36 PM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any changes destined for v5.13 to your linux-next
> included branches until after v5.12-rc1 has been released.
>
> Changes since 20210223:
>
on i386:
ERROR: modpost: "__udivdi3" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] u
Hi all,
Please do not add any changes destined for v5.13 to your linux-next
included branches until after v5.12-rc1 has been released.
Changes since 20210223:
The risc-v tree gained a conflict against Linus' tree.
The amdgpu tree lost its build failure.
The block tree lost its build failure.
On 02/23/17 19:01, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material intended for v4.12 to your linux-next
> included branches until after v4.11-rc1 has been released.
>
> Changes since 20170223:
>
on i386, when CONFIG_LBDAF is not enabled:
../fs/nfs/blocklayout/blocklayout.
Hi all,
Please do not add any material intended for v4.12 to your linux-next
included branches until after v4.11-rc1 has been released.
Changes since 20170223:
The drm tree gained a conflict against Linus' tree and a build failure,
so I used the version from next-20170223.
The scsi tree still h
On Wed, Feb 24, 2016 at 3:37 PM, Benjamin LaHaise wrote:
> On Wed, Feb 24, 2016 at 07:32:17AM +0100, Sedat Dilek wrote:
>> On Wed, Feb 24, 2016 at 6:34 AM, Stephen Rothwell
>> wrote:
>> > Hi all,
>> >
>> > Changes since 20160223:
>> >
>> ...
>> > The aio tree still had a build failure so I used
Hi Sedat,
On Thu, 17 Mar 2016 11:21:56 +0100 Sedat Dilek wrote:
>
> not seeing this anymore.
> How was that solved?
The code has been removed while it is further worked on and reviewed
and may reappear after -rc1 is released.
--
Cheers,
Stephen Rothwell
On Thu, Mar 17, 2016 at 11:27 AM, Stephen Rothwell
wrote:
> Hi Sedat,
>
> On Thu, 17 Mar 2016 11:21:56 +0100 Sedat Dilek wrote:
>>
>> not seeing this anymore.
>> How was that solved?
>
> The code has been removed while it is further worked on and reviewed
> and may reappear after -rc1 is release
On Wed, Feb 24, 2016 at 07:32:17AM +0100, Sedat Dilek wrote:
> On Wed, Feb 24, 2016 at 6:34 AM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > Changes since 20160223:
> >
> ...
> > The aio tree still had a build failure so I used the version from
> > next-20160111.
> >
>
> Might be good to poke t
On Wed, Feb 24, 2016 at 6:34 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160223:
>
...
> The aio tree still had a build failure so I used the version from
> next-20160111.
>
Might be good to poke the maintainer as I am seeing this for a long
time in Linux-next.
- Sedat -
Hi all,
Changes since 20160223:
The arc tree gained conflicts against the arc-current tree.
The pci tree gained a conflict against the pci-current tree.
The mac80211-next tree gained a build failure so I used the version
from next-20160223.
The kvm-arm tree gained a conflict against the arm64
- Original Message -
> On Tue, Feb 24, 2015 at 02:02:57PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20150223:
> >
> > The hid tree gained a conflict against Linus' tree.
> >
> > The drm-misc tree gained a build failure for which I applied a merge
> > fix patch.
> >
On Tue, Feb 24, 2015 at 02:02:57PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150223:
>
> The hid tree gained a conflict against Linus' tree.
>
> The drm-misc tree gained a build failure for which I applied a merge
> fix patch.
>
> Non-merge commits (relative to Linus' tree):
Hi all,
Changes since 20150223:
The hid tree gained a conflict against Linus' tree.
The drm-misc tree gained a build failure for which I applied a merge
fix patch.
Non-merge commits (relative to Linus' tree): 1108
718 files changed, 18557 insertions(+), 17357 deletions(-)
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140221:
The mvebu tree gained a conflict against Linus' tree.
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The sound
Hi,
On Tue, 26 Feb 2013 06:00:24 +0100 Sedat Dilek wrote:
>
> February 26th...
Yeah :-(
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpBu5C4PhYDA.pgp
Description: PGP signature
February 26th...
- Sedat -
On Tue, Feb 26, 2013 at 4:16 AM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any work destined for v3.10 to your -next included
> branches until after Linus has release v3.9-rc1.
>
> Changes since 20130223:
>
> The kbuild tree lost its build failure.
>
> Th
Hi all,
Please do not add any work destined for v3.10 to your -next included
branches until after Linus has release v3.9-rc1.
Changes since 20130223:
The kbuild tree lost its build failure.
The infiniband tree gained a conflict against Linus' tree.
The drm tree still has its build failure for
On Tue, 26 Feb 2008, Stephen Rothwell wrote:
> On Mon, 25 Feb 2008 22:56:04 +0100 (CET) Geert Uytterhoeven <[EMAIL
> PROTECTED]> wrote:
> >
> > Can you please add
> > http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-patches-2.6/series?
> > So far there's only one patch in between NEXT_PATCHES_{START
Hi Geert,
On Mon, 25 Feb 2008 22:56:04 +0100 (CET) Geert Uytterhoeven <[EMAIL PROTECTED]>
wrote:
>
> Can you please add
> http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-patches-2.6/series?
> So far there's only one patch in between NEXT_PATCHES_{START,END} yet,
> though.
Added, thanks.
> Ah, I
On Mon, 25 Feb 2008 22:56:04 +0100 (CET) Geert Uytterhoeven wrote:
> P.S. For the interested, a script to update the SHA1 in the quilt series file:
Thanks, anakin.
Version to update $BASE based on current kernel tree is attached.
---
~Randy
quilt-update-tree-base
Description: Binary data
On Sun, 24 Feb 2008, Stephen Rothwell wrote:
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also quilt-import.log and merge.
Hi!
> > velocity_suspend() seems to be at fault.
>
> (gdb) l *(velocity_suspend+0x37)
> 0xc0244665 is in velocity_suspend (drivers/net/via-velocity.c:3399).
> 3394 if(!netif_running(vptr->dev))
> 3395 return 0;
> 3396
> 3397 netif_device_detach(vptr->dev);
> 3
Hi Frank,
On Mon, 25 Feb 2008 11:12:45 +0100 Frank Seidel <[EMAIL PROTECTED]> wrote:
>
> Stephen Rothwell wrote:
> > I have created today's linux-next tree at
>
> i bet your $SUBJECT was meant for the Tree for Feb 25, wasn't it?
> ;-)
Damn! I remembered to reread to body of the mail and forgot
Hi,
Stephen Rothwell wrote:
> I have created today's linux-next tree at
i bet your $SUBJECT was meant for the Tree for Feb 25, wasn't it?
;-)
Thanks,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each
Rafael J. Wysocki wrote:
> On Monday, 25 of February 2008, Kevin Winchester wrote:
>> Rafael J. Wysocki wrote:
>>> On Sunday, 24 of February 2008, Kevin Winchester wrote:
>>>
Today was different - I attempted to suspend and resume from the console,
and the machine did not come back up. I
On Monday, 25 of February 2008, Kevin Winchester wrote:
> Rafael J. Wysocki wrote:
> > On Sunday, 24 of February 2008, Kevin Winchester wrote:
> >
> >> Today was different - I attempted to suspend and resume from the console,
> >> and the machine did not come back up. I found the following in my
Rafael J. Wysocki wrote:
> On Sunday, 24 of February 2008, Kevin Winchester wrote:
>
>> Today was different - I attempted to suspend and resume from the console,
>> and the machine did not come back up. I found the following in my log -
>> any help would be appreciated.
>>
>> Feb 24 13:59:56 alek
On Sunday, 24 of February 2008, Kevin Winchester wrote:
> Stephen Rothwell wrote:
> > Hi all,
Hi,
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
> >
> > You can see which trees have been included by looking in the Next/Trees
>
Stephen Rothwell wrote:
> Hi all,
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source. There are also quilt-import.log and merge.log file
Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each
31 matches
Mail list logo
