On 8/1/19 10:52 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190801:
>
on x86_64:
when CONFIG_OF is not set/enabled.
WARNING: unmet direct dependencies detected for MDIO_OCTEON
Depends on [n]: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && 64BIT
[=y] && HAS_IOMEM [=y]
Hi all,
Changes since 20190801:
My fixes tree is empty again
The jc_docs tree gained a conflict against the cifs tree.
The drm-misc tree lost its build failure.
The tip tree lost its build failure.
Non-merge commits (relative to Linus' tree): 3729
4234 files changed, 221424 insertions(+),
On Thu, Aug 02, 2018 at 09:10:11PM +0200, Máté Eckl wrote:
> On Thu, Aug 02, 2018 at 09:05:57PM +0200, Máté Eckl wrote:
> > Hi Randy,
> >
> > Thanks for reporting!
> >
> > Please find the patch attached.
>
> Sorry I made an error in the commit message... See the fix below.
Please, resubmit
On Thu, Aug 02, 2018 at 09:10:11PM +0200, Máté Eckl wrote:
> On Thu, Aug 02, 2018 at 09:05:57PM +0200, Máté Eckl wrote:
> > Hi Randy,
> >
> > Thanks for reporting!
> >
> > Please find the patch attached.
>
> Sorry I made an error in the commit message... See the fix below.
Please, resubmit
Hi all,
Changes since 20180801:
The powerpc tree gained a conflict against the m68k tree.
The vfs tree gained conflicts against the btrfs-kdave tree.
The jc_docs tree gained a conflict against the ext4 tree.
The net-next tree gained a conflict against the rdma tree.
The staging tree still
Hi all,
Changes since 20180801:
The powerpc tree gained a conflict against the m68k tree.
The vfs tree gained conflicts against the btrfs-kdave tree.
The jc_docs tree gained a conflict against the ext4 tree.
The net-next tree gained a conflict against the rdma tree.
The staging tree still
Hi all,
Changes since 20170801:
The drm-misc tree gained a conflict against Linus' tree.
The tip tree gained a conflict against the fbdev tree.
The tty tree gained a conflict against the tty.current tree.
I again reverted a commit from the staging tree that was causing overnight
build
Hi all,
Changes since 20170801:
The drm-misc tree gained a conflict against Linus' tree.
The tip tree gained a conflict against the fbdev tree.
The tty tree gained a conflict against the tty.current tree.
I again reverted a commit from the staging tree that was causing overnight
build
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 20160801:
My fixes tree contains:
clocksource/drivers/clps_711x: fixup for "ARM: clps711x: Switch to
MULTIPLATFORM"
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 20160801:
My fixes tree contains:
clocksource/drivers/clps_711x: fixup for "ARM: clps711x: Switch to
MULTIPLATFORM"
The akpm tree gained a
Hi all,
Changes since 20130801:
The ext4 tree still has its build failure so I used the version from
next-20130726.
The usb-gadget tree gained a conflict against the usb tree.
I have created today's linux-next tree
Hi all,
Changes since 20130801:
The ext4 tree still has its build failure so I used the version from
next-20130726.
The usb-gadget tree gained a conflict against the usb tree.
I have created today's linux-next tree
On Thu, 02 Aug 2012 08:55:30 -0700 Randy Dunlap wrote:
> On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Please do not add anything to linux-next included branches/series that is
> > destined for v3.7 until after v3.6-rc1 is released.
> >
> > Reminder: do not rebase your
On Thu, Aug 02, 2012 at 11:36:16AM -0500, Seth Forshee wrote:
> On Thu, Aug 02, 2012 at 11:31:54AM -0500, Seth Forshee wrote:
> > On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
> > > On 08/02/2012 09:15 AM, Seth Forshee wrote:
> > >
> > > > On Thu, Aug 02, 2012 at 09:07:04AM -0700,
On Thu, Aug 02, 2012 at 11:31:54AM -0500, Seth Forshee wrote:
> The functions in question are built or not based off of ACPI_VIDEO,
> which in turn depends on ACPI. So if ACPI=n, then ACPI_VIDEO=n and you
> can't configure APPLE_GMUX=(m|y). Is that right, or am I missing
> something?
On 08/02/2012 09:31 AM, Seth Forshee wrote:
> On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
>> On 08/02/2012 09:15 AM, Seth Forshee wrote:
>>
>>> On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
> Hi all,
On Thu, Aug 02, 2012 at 11:31:54AM -0500, Seth Forshee wrote:
> On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
> > On 08/02/2012 09:15 AM, Seth Forshee wrote:
> >
> > > On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
> > >> On 08/01/2012 09:15 PM, Stephen Rothwell
On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
> On 08/02/2012 09:15 AM, Seth Forshee wrote:
>
> > On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
> >> On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
> >>
> >>> Hi all,
> >>>
> >>> Please do not add anything to
On 08/02/2012 09:15 AM, Seth Forshee wrote:
> On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
>> On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> Please do not add anything to linux-next included branches/series that is
>>> destined for v3.7 until after
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
> On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Please do not add anything to linux-next included branches/series that is
> > destined for v3.7 until after v3.6-rc1 is released.
> >
> > Reminder: do not rebase
Cc:ing Corentin:
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
> when CONFIG_ACPI is not enabled: (on i386)
>
> drivers/platform/x86/apple-gmux.c: In function 'gmux_probe':
> drivers/platform/x86/apple-gmux.c:196:2: error: implicit declaration of
> function
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add anything to linux-next included branches/series that is
> destined for v3.7 until after v3.6-rc1 is released.
>
> Reminder: do not rebase your branches before asking Linus to pull them ...
>
> Changes since
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add anything to linux-next included branches/series that is
> destined for v3.7 until after v3.6-rc1 is released.
>
> Reminder: do not rebase your branches before asking Linus to pull them ...
>
> Changes since
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not rebase your branches before asking Linus to pull them ...
Changes since 20120731:
on
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not rebase your branches before asking Linus to pull them ...
Changes since 20120731:
Cc:ing Corentin:
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
when CONFIG_ACPI is not enabled: (on i386)
drivers/platform/x86/apple-gmux.c: In function 'gmux_probe':
drivers/platform/x86/apple-gmux.c:196:2: error: implicit declaration of
function
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not rebase your branches
On 08/02/2012 09:15 AM, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
On 08/02/2012 09:15 AM, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
Hi all,
Please do not add anything to linux-next included
On Thu, Aug 02, 2012 at 11:31:54AM -0500, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
On 08/02/2012 09:15 AM, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
Hi
On 08/02/2012 09:31 AM, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
On 08/02/2012 09:15 AM, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap wrote:
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
Hi all,
Please do not add
On Thu, Aug 02, 2012 at 11:31:54AM -0500, Seth Forshee wrote:
The functions in question are built or not based off of ACPI_VIDEO,
which in turn depends on ACPI. So if ACPI=n, then ACPI_VIDEO=n and you
can't configure APPLE_GMUX=(m|y). Is that right, or am I missing
something?
On Thu, Aug 02, 2012 at 11:36:16AM -0500, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 11:31:54AM -0500, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 09:19:30AM -0700, Randy Dunlap wrote:
On 08/02/2012 09:15 AM, Seth Forshee wrote:
On Thu, Aug 02, 2012 at 09:07:04AM -0700, Randy Dunlap
On Thu, 02 Aug 2012 08:55:30 -0700 Randy Dunlap rdun...@xenotime.net wrote:
On 08/01/2012 09:15 PM, Stephen Rothwell wrote:
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not rebase your branches before asking Linus to pull them ...
Changes since 20120731:
Removed trees: samsung, bjdooks-i2c (unfetchable)
Linus'
Hi all,
Please do not add anything to linux-next included branches/series that is
destined for v3.7 until after v3.6-rc1 is released.
Reminder: do not rebase your branches before asking Linus to pull them ...
Changes since 20120731:
Removed trees: samsung, bjdooks-i2c (unfetchable)
Linus'
36 matches
Mail list logo
