Re: mmotm 2013-06-05-17-24 uploaded (rtc)

2013-06-06 Thread Andrew Morton 
On Wed, 05 Jun 2013 21:31:46 -0700 Randy Dunlap  wrote:

> On 06/05/13 17:26, a...@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
> > 
> >http://www.ozlabs.org/~akpm/mmotm/
> > 
> > mmotm-readme.txt says
> > 
> > README for mm-of-the-moment:
> > 
> > http://www.ozlabs.org/~akpm/mmotm/
> > 
> 
> on i386 when CONFIG_PM is not enabled:
> 
> drivers/rtc/class.c:339:18: error: lvalue required as unary '&' operand
> 
> due to:
> #define rtc_class_dev_pm_ops  NULL

hm, OK, thanks.  Shuah's "drivers/rtc/class: convert from Legacy pm ops
to dev_pm_ops" is busted and I'm not seeing a quick fix - the ifdeffery
in drivers/rtc/class.c is a bit odd (uses CONFIG_PM instead of
CONFIG_PM_SLEEP, for a start).  I'll drop it.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded (ptp_pch)

2013-06-06 Thread Ben Hutchings 
On Wed, 2013-06-05 at 21:37 -0700, Randy Dunlap wrote:
> On 06/05/13 17:26, a...@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
> > 
> >http://www.ozlabs.org/~akpm/mmotm/
> > 
> > mmotm-readme.txt says
> > 
> > README for mm-of-the-moment:
> > 
> > http://www.ozlabs.org/~akpm/mmotm/
> > 
> 
> on i386:  when CONFIG_PCI is not enabled:
> 
> drivers/ptp/ptp_pch.c:710:1: warning: data definition has no type or storage 
> class [enabled by default]
> drivers/ptp/ptp_pch.c:710:1: warning: type defaults to 'int' in declaration 
> of 'module_pci_driver' [-Wimplicit-int]
> drivers/ptp/ptp_pch.c:710:1: warning: parameter names (without types) in 
> function declaration [enabled by default]
> drivers/ptp/ptp_pch.c:701:26: warning: 'pch_driver' defined but not used 
> [-Wunused-variable]

Right, it should depend on CONFIG_PCI.  Previously reported in
 but there was then
some confusion about whether it was s390 breakage (which it isn't).

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded

2013-06-06 Thread Robin Holt 
On Wed, Jun 05, 2013 at 05:26:36PM -0700, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
> 
>http://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> http://www.ozlabs.org/~akpm/mmotm/
> 
> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> more than once a week.
> 
> You will need quilt to apply these patches to the latest Linus release (3.x
> or 3.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series

It looks like the shutdown-reboot patches I sent are still not queued
for Linus.  Did these just get lost in the shuffle or do they need to
be resubmitted?  The first two were marked for -stable and I would really
like to get them in sometime as it does affect severely affect shutdown
of large systems.  I will resend them shortly.

Robin

> 
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE--mm-dd-hh-mm-ss.  Both contain the string -mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
> 
> This tree is partially included in linux-next.  To see which patches are
> included in linux-next, consult the `series' file.  Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
> 
> A git tree which contains the memory management portion of this tree is
> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> by Michal Hocko.  It contains the patches which are between the
> "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
> file, http://www.ozlabs.org/~akpm/mmotm/series.
> 
> 
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release.  Individual mmotm releases are tagged.  The master branch always
> points to the latest release, so it's constantly rebasing.
> 
> http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary
> 
> To develop on top of mmotm git:
> 
>   $ git remote add mmotm 
> git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
>   $ git remote update mmotm
>   $ git checkout -b topic mmotm/master
>   
>   $ git send-email mmotm/master.. [...]
> 
> To rebase a branch with older patches to a new mmotm release:
> 
>   $ git remote update mmotm
>   $ git rebase --onto mmotm/master  topic
> 
> 
> 
> 
> The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> contains daily snapshots of the -mm tree.  It is updated more frequently
> than mmotm, and is untested.
> 
> A git copy of this tree is available at
> 
>   http://git.cmpxchg.org/?p=linux-mmots.git;a=summary
> 
> and use of this tree is similar to
> http://git.cmpxchg.org/?p=linux-mmotm.git, described above.
> 
> 
> This mmotm tree contains the following patches against 3.10-rc4:
> (patches marked "*" will be included in linux-next)
> 
>   origin.patch
>   linux-next.patch
>   linux-next-git-rejects.patch
>   arch-alpha-kernel-systblss-remove-debug-check.patch
>   i-need-old-gcc.patch
> * cpu-hotplug-provide-a-generic-helper-to-disable-enable-cpu-hotplug.patch
> * cpu-hotplug-provide-a-generic-helper-to-disable-enable-cpu-hotplug-v11.patch
> * migrate-shutdown-reboot-to-boot-cpu.patch
> * migrate-shutdown-reboot-to-boot-cpu-v11.patch
> * kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg.patch
> * kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg-fix.patch
> * 
> lib-mpi-mpicoderc-looping-issue-need-stop-when-equal-to-zero-found-by-extra_flags=-w.patch
> * ocfs2-ocfs2_prep_new_orphaned_file-should-return-ret.patch
> * memcg-dont-initialize-kmem-cache-destroying-work-for-root-caches.patch
> * rtc-tps6586x-device-wakeup-flags-correction.patch
> * drivers-rtc-rtc-cmosc-fix-accidentally-enabling-rtc-channel.patch
> * drivers-rtc-rtc-cmosc-fix-accidentally-enabling-rtc-channel-fix.patch
> * audit-wait_for_auditd-should-use-task_uninterruptible.patch
> * cciss-fix-broken-mutex-usage-in-ioctl.patch
> * 
> drivers-rtc-rtc-twlc-fix-missing-device_init_wakeup-when-booted-with-device-tree.patch
> * 
> swap-avoid-read_swap_cache_async-race-to-deadlock-while-waiting-on-discard-i-o-completion.patch
> * 
> fs-ocfs2-nameic-remove-unecessary-error-when-removing-non-empty-directory.patch
> * rtc-at91rm9200-add-match-table-compile-guard.patch
> * rtc-at91rm9200-add-configuration-support.patch
> * rtc-at91rm9200-refactor-interrupt-register-handling.patch
> * rtc-at91rm9200-add-shadow-interrupt-mask.patch
> * rtc-at91rm9200-use-shadow-imr-on-at91sam9x5.patch
> * aio-use-call_rcu-instead-of-synchronize_rcu-in-kill_ioctx.patch
> * drivers-misc-sgi-gru-grufilec-fix-info-leak-in-gru_get_config_info.patch
> * mm-page_alloc-fix-watermark-check-in-__zone_watermark_ok.patch
> * mm-migration-add-migrate_entry_wait_huge.patch
> * drivers-base-cpuc-fix-maxcpus-boot-option.patch
> *

Re: mmotm 2013-06-05-17-24 uploaded

2013-06-06 Thread Stephen Rothwell 
Hi Geert,

On Thu, 6 Jun 2013 09:23:10 +0200 Geert Uytterhoeven  
wrote:
>
> Do you have "git rerere" enabled?

Not in the tree that I do the import in.  I clone a new tree for that.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au


pgpNw6Vf7cwl2.pgp
Description: PGP signature

Re: mmotm 2013-06-05-17-24 uploaded

2013-06-06 Thread Geert Uytterhoeven 
Hi Andrew,

On Thu, Jun 6, 2013 at 4:04 AM, Stephen Rothwell  wrote:
> On Wed, 05 Jun 2013 17:26:36 -0700 a...@linux-foundation.org wrote:
>>
>>   linux-next-git-rejects.patch
>
> We must figure out why you sometimes get rejects that I do not get when I
> import your series into a git tree.  However in this case you resolution
> is not quite right.  It leaves 2 continue statements in
> net/mac80211/iface.c at line 191 which will unconditionally short circuit
> the enclosing loop.  The version that will be in linux-next today is
> correct (and git did it automatically as part of the merge of the old
> linux-next tree).

Do you have "git rerere" enabled?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded

2013-06-06 Thread Geert Uytterhoeven 
Hi Andrew,

On Thu, Jun 6, 2013 at 4:04 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
 On Wed, 05 Jun 2013 17:26:36 -0700 a...@linux-foundation.org wrote:

   linux-next-git-rejects.patch

 We must figure out why you sometimes get rejects that I do not get when I
 import your series into a git tree.  However in this case you resolution
 is not quite right.  It leaves 2 continue statements in
 net/mac80211/iface.c at line 191 which will unconditionally short circuit
 the enclosing loop.  The version that will be in linux-next today is
 correct (and git did it automatically as part of the merge of the old
 linux-next tree).

Do you have git rerere enabled?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded

2013-06-06 Thread Stephen Rothwell 
Hi Geert,

On Thu, 6 Jun 2013 09:23:10 +0200 Geert Uytterhoeven ge...@linux-m68k.org 
wrote:

 Do you have git rerere enabled?

Not in the tree that I do the import in.  I clone a new tree for that.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au


pgpNw6Vf7cwl2.pgp
Description: PGP signature

Re: mmotm 2013-06-05-17-24 uploaded

2013-06-06 Thread Robin Holt 
On Wed, Jun 05, 2013 at 05:26:36PM -0700, a...@linux-foundation.org wrote:
 The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
 
http://www.ozlabs.org/~akpm/mmotm/
 
 mmotm-readme.txt says
 
 README for mm-of-the-moment:
 
 http://www.ozlabs.org/~akpm/mmotm/
 
 This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
 more than once a week.
 
 You will need quilt to apply these patches to the latest Linus release (3.x
 or 3.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
 http://ozlabs.org/~akpm/mmotm/series

It looks like the shutdown-reboot patches I sent are still not queued
for Linus.  Did these just get lost in the shuffle or do they need to
be resubmitted?  The first two were marked for -stable and I would really
like to get them in sometime as it does affect severely affect shutdown
of large systems.  I will resend them shortly.

Robin

 
 The file broken-out.tar.gz contains two datestamp files: .DATE and
 .DATE--mm-dd-hh-mm-ss.  Both contain the string -mm-dd-hh-mm-ss,
 followed by the base kernel version against which this patch series is to
 be applied.
 
 This tree is partially included in linux-next.  To see which patches are
 included in linux-next, consult the `series' file.  Only the patches
 within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
 linux-next.
 
 A git tree which contains the memory management portion of this tree is
 maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
 by Michal Hocko.  It contains the patches which are between the
 #NEXT_PATCHES_START mm and #NEXT_PATCHES_END markers, from the series
 file, http://www.ozlabs.org/~akpm/mmotm/series.
 
 
 A full copy of the full kernel tree with the linux-next and mmotm patches
 already applied is available through git within an hour of the mmotm
 release.  Individual mmotm releases are tagged.  The master branch always
 points to the latest release, so it's constantly rebasing.
 
 http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary
 
 To develop on top of mmotm git:
 
   $ git remote add mmotm 
 git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
   $ git remote update mmotm
   $ git checkout -b topic mmotm/master
   make changes, commit
   $ git send-email mmotm/master.. [...]
 
 To rebase a branch with older patches to a new mmotm release:
 
   $ git remote update mmotm
   $ git rebase --onto mmotm/master topic base topic
 
 
 
 
 The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
 contains daily snapshots of the -mm tree.  It is updated more frequently
 than mmotm, and is untested.
 
 A git copy of this tree is available at
 
   http://git.cmpxchg.org/?p=linux-mmots.git;a=summary
 
 and use of this tree is similar to
 http://git.cmpxchg.org/?p=linux-mmotm.git, described above.
 
 
 This mmotm tree contains the following patches against 3.10-rc4:
 (patches marked * will be included in linux-next)
 
   origin.patch
   linux-next.patch
   linux-next-git-rejects.patch
   arch-alpha-kernel-systblss-remove-debug-check.patch
   i-need-old-gcc.patch
 * cpu-hotplug-provide-a-generic-helper-to-disable-enable-cpu-hotplug.patch
 * cpu-hotplug-provide-a-generic-helper-to-disable-enable-cpu-hotplug-v11.patch
 * migrate-shutdown-reboot-to-boot-cpu.patch
 * migrate-shutdown-reboot-to-boot-cpu-v11.patch
 * kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg.patch
 * kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg-fix.patch
 * 
 lib-mpi-mpicoderc-looping-issue-need-stop-when-equal-to-zero-found-by-extra_flags=-w.patch
 * ocfs2-ocfs2_prep_new_orphaned_file-should-return-ret.patch
 * memcg-dont-initialize-kmem-cache-destroying-work-for-root-caches.patch
 * rtc-tps6586x-device-wakeup-flags-correction.patch
 * drivers-rtc-rtc-cmosc-fix-accidentally-enabling-rtc-channel.patch
 * drivers-rtc-rtc-cmosc-fix-accidentally-enabling-rtc-channel-fix.patch
 * audit-wait_for_auditd-should-use-task_uninterruptible.patch
 * cciss-fix-broken-mutex-usage-in-ioctl.patch
 * 
 drivers-rtc-rtc-twlc-fix-missing-device_init_wakeup-when-booted-with-device-tree.patch
 * 
 swap-avoid-read_swap_cache_async-race-to-deadlock-while-waiting-on-discard-i-o-completion.patch
 * 
 fs-ocfs2-nameic-remove-unecessary-error-when-removing-non-empty-directory.patch
 * rtc-at91rm9200-add-match-table-compile-guard.patch
 * rtc-at91rm9200-add-configuration-support.patch
 * rtc-at91rm9200-refactor-interrupt-register-handling.patch
 * rtc-at91rm9200-add-shadow-interrupt-mask.patch
 * rtc-at91rm9200-use-shadow-imr-on-at91sam9x5.patch
 * aio-use-call_rcu-instead-of-synchronize_rcu-in-kill_ioctx.patch
 * drivers-misc-sgi-gru-grufilec-fix-info-leak-in-gru_get_config_info.patch
 * mm-page_alloc-fix-watermark-check-in-__zone_watermark_ok.patch
 * mm-migration-add-migrate_entry_wait_huge.patch
 * drivers-base-cpuc-fix-maxcpus-boot-option.patch
 * drivers-base-cpuc-fix-maxcpus-boot-option-fix.patch
 *

Re: mmotm 2013-06-05-17-24 uploaded (ptp_pch)

2013-06-06 Thread Ben Hutchings 
On Wed, 2013-06-05 at 21:37 -0700, Randy Dunlap wrote:
 On 06/05/13 17:26, a...@linux-foundation.org wrote:
  The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
  
 http://www.ozlabs.org/~akpm/mmotm/
  
  mmotm-readme.txt says
  
  README for mm-of-the-moment:
  
  http://www.ozlabs.org/~akpm/mmotm/
  
 
 on i386:  when CONFIG_PCI is not enabled:
 
 drivers/ptp/ptp_pch.c:710:1: warning: data definition has no type or storage 
 class [enabled by default]
 drivers/ptp/ptp_pch.c:710:1: warning: type defaults to 'int' in declaration 
 of 'module_pci_driver' [-Wimplicit-int]
 drivers/ptp/ptp_pch.c:710:1: warning: parameter names (without types) in 
 function declaration [enabled by default]
 drivers/ptp/ptp_pch.c:701:26: warning: 'pch_driver' defined but not used 
 [-Wunused-variable]

Right, it should depend on CONFIG_PCI.  Previously reported in
http://thread.gmane.org/gmane.linux.network/270531 but there was then
some confusion about whether it was s390 breakage (which it isn't).

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded (rtc)

2013-06-06 Thread Andrew Morton 
On Wed, 05 Jun 2013 21:31:46 -0700 Randy Dunlap rdun...@infradead.org wrote:

 On 06/05/13 17:26, a...@linux-foundation.org wrote:
  The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
  
 http://www.ozlabs.org/~akpm/mmotm/
  
  mmotm-readme.txt says
  
  README for mm-of-the-moment:
  
  http://www.ozlabs.org/~akpm/mmotm/
  
 
 on i386 when CONFIG_PM is not enabled:
 
 drivers/rtc/class.c:339:18: error: lvalue required as unary '' operand
 
 due to:
 #define rtc_class_dev_pm_ops  NULL

hm, OK, thanks.  Shuah's drivers/rtc/class: convert from Legacy pm ops
to dev_pm_ops is busted and I'm not seeing a quick fix - the ifdeffery
in drivers/rtc/class.c is a bit odd (uses CONFIG_PM instead of
CONFIG_PM_SLEEP, for a start).  I'll drop it.

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded (ptp_pch)

2013-06-05 Thread Randy Dunlap 
On 06/05/13 17:26, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
> 
>http://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> http://www.ozlabs.org/~akpm/mmotm/
> 

on i386:  when CONFIG_PCI is not enabled:

drivers/ptp/ptp_pch.c:710:1: warning: data definition has no type or storage 
class [enabled by default]
drivers/ptp/ptp_pch.c:710:1: warning: type defaults to 'int' in declaration of 
'module_pci_driver' [-Wimplicit-int]
drivers/ptp/ptp_pch.c:710:1: warning: parameter names (without types) in 
function declaration [enabled by default]
drivers/ptp/ptp_pch.c:701:26: warning: 'pch_driver' defined but not used 
[-Wunused-variable]


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded (rtc)

2013-06-05 Thread Randy Dunlap 
On 06/05/13 17:26, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
> 
>http://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> http://www.ozlabs.org/~akpm/mmotm/
> 

on i386 when CONFIG_PM is not enabled:

drivers/rtc/class.c:339:18: error: lvalue required as unary '&' operand

due to:
#define rtc_class_dev_pm_opsNULL



-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded

2013-06-05 Thread Stephen Rothwell 
Hi Andrew,

On Wed, 05 Jun 2013 17:26:36 -0700 a...@linux-foundation.org wrote:
>
>   linux-next-git-rejects.patch

We must figure out why you sometimes get rejects that I do not get when I
import your series into a git tree.  However in this case you resolution
is not quite right.  It leaves 2 continue statements in
net/mac80211/iface.c at line 191 which will unconditionally short circuit
the enclosing loop.  The version that will be in linux-next today is
correct (and git did it automatically as part of the merge of the old
linux-next tree).

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au


pgp6hFfBMo28T.pgp
Description: PGP signature

mmotm 2013-06-05-17-24 uploaded

2013-06-05 Thread akpm 
The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to

   http://www.ozlabs.org/~akpm/mmotm/

mmotm-readme.txt says

README for mm-of-the-moment:

http://www.ozlabs.org/~akpm/mmotm/

This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
more than once a week.

You will need quilt to apply these patches to the latest Linus release (3.x
or 3.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
http://ozlabs.org/~akpm/mmotm/series

The file broken-out.tar.gz contains two datestamp files: .DATE and
.DATE--mm-dd-hh-mm-ss.  Both contain the string -mm-dd-hh-mm-ss,
followed by the base kernel version against which this patch series is to
be applied.

This tree is partially included in linux-next.  To see which patches are
included in linux-next, consult the `series' file.  Only the patches
within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
linux-next.

A git tree which contains the memory management portion of this tree is
maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
by Michal Hocko.  It contains the patches which are between the
"#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series
file, http://www.ozlabs.org/~akpm/mmotm/series.


A full copy of the full kernel tree with the linux-next and mmotm patches
already applied is available through git within an hour of the mmotm
release.  Individual mmotm releases are tagged.  The master branch always
points to the latest release, so it's constantly rebasing.

http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary

To develop on top of mmotm git:

  $ git remote add mmotm 
git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
  $ git remote update mmotm
  $ git checkout -b topic mmotm/master
  
  $ git send-email mmotm/master.. [...]

To rebase a branch with older patches to a new mmotm release:

  $ git remote update mmotm
  $ git rebase --onto mmotm/master  topic




The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
contains daily snapshots of the -mm tree.  It is updated more frequently
than mmotm, and is untested.

A git copy of this tree is available at

http://git.cmpxchg.org/?p=linux-mmots.git;a=summary

and use of this tree is similar to
http://git.cmpxchg.org/?p=linux-mmotm.git, described above.


This mmotm tree contains the following patches against 3.10-rc4:
(patches marked "*" will be included in linux-next)

  origin.patch
  linux-next.patch
  linux-next-git-rejects.patch
  arch-alpha-kernel-systblss-remove-debug-check.patch
  i-need-old-gcc.patch
* cpu-hotplug-provide-a-generic-helper-to-disable-enable-cpu-hotplug.patch
* cpu-hotplug-provide-a-generic-helper-to-disable-enable-cpu-hotplug-v11.patch
* migrate-shutdown-reboot-to-boot-cpu.patch
* migrate-shutdown-reboot-to-boot-cpu-v11.patch
* kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg.patch
* kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg-fix.patch
* 
lib-mpi-mpicoderc-looping-issue-need-stop-when-equal-to-zero-found-by-extra_flags=-w.patch
* ocfs2-ocfs2_prep_new_orphaned_file-should-return-ret.patch
* memcg-dont-initialize-kmem-cache-destroying-work-for-root-caches.patch
* rtc-tps6586x-device-wakeup-flags-correction.patch
* drivers-rtc-rtc-cmosc-fix-accidentally-enabling-rtc-channel.patch
* drivers-rtc-rtc-cmosc-fix-accidentally-enabling-rtc-channel-fix.patch
* audit-wait_for_auditd-should-use-task_uninterruptible.patch
* cciss-fix-broken-mutex-usage-in-ioctl.patch
* 
drivers-rtc-rtc-twlc-fix-missing-device_init_wakeup-when-booted-with-device-tree.patch
* 
swap-avoid-read_swap_cache_async-race-to-deadlock-while-waiting-on-discard-i-o-completion.patch
* 
fs-ocfs2-nameic-remove-unecessary-error-when-removing-non-empty-directory.patch
* rtc-at91rm9200-add-match-table-compile-guard.patch
* rtc-at91rm9200-add-configuration-support.patch
* rtc-at91rm9200-refactor-interrupt-register-handling.patch
* rtc-at91rm9200-add-shadow-interrupt-mask.patch
* rtc-at91rm9200-use-shadow-imr-on-at91sam9x5.patch
* aio-use-call_rcu-instead-of-synchronize_rcu-in-kill_ioctx.patch
* drivers-misc-sgi-gru-grufilec-fix-info-leak-in-gru_get_config_info.patch
* mm-page_alloc-fix-watermark-check-in-__zone_watermark_ok.patch
* mm-migration-add-migrate_entry_wait_huge.patch
* drivers-base-cpuc-fix-maxcpus-boot-option.patch
* drivers-base-cpuc-fix-maxcpus-boot-option-fix.patch
* kernel-audit_treec-audit_add_tree_rule-protect-rule-from-kill_rules.patch
* frontswap-fix-incorrect-zeroing-and-allocation-size-for-frontswap_map.patch
* mm-memcontrol-fix-lockless-reclaim-hierarchy-iterator.patch
* drivers-platform-x86-intel_ips-convert-to-module_pci_driver.patch
* sound-soc-codecs-si476xc-dont-use-0bnnn.patch
* x86-make-mem=-option-to-work-for-efi-platform.patch
* 
audit-fix-mq_open-and-mq_unlink-to-add-the-mq-root-as-a-hidden-parent-audit_names-record.patch
* kernel-auditfilterc-fixing-build-warning.patch
* kernel-auditfilterc-fix-leak-in-audit_add_rule-error-path.patch
*

mmotm 2013-06-05-17-24 uploaded

2013-06-05 Thread akpm 
The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to

   http://www.ozlabs.org/~akpm/mmotm/

mmotm-readme.txt says

README for mm-of-the-moment:

http://www.ozlabs.org/~akpm/mmotm/

This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
more than once a week.

You will need quilt to apply these patches to the latest Linus release (3.x
or 3.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
http://ozlabs.org/~akpm/mmotm/series

The file broken-out.tar.gz contains two datestamp files: .DATE and
.DATE--mm-dd-hh-mm-ss.  Both contain the string -mm-dd-hh-mm-ss,
followed by the base kernel version against which this patch series is to
be applied.

This tree is partially included in linux-next.  To see which patches are
included in linux-next, consult the `series' file.  Only the patches
within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
linux-next.

A git tree which contains the memory management portion of this tree is
maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
by Michal Hocko.  It contains the patches which are between the
#NEXT_PATCHES_START mm and #NEXT_PATCHES_END markers, from the series
file, http://www.ozlabs.org/~akpm/mmotm/series.


A full copy of the full kernel tree with the linux-next and mmotm patches
already applied is available through git within an hour of the mmotm
release.  Individual mmotm releases are tagged.  The master branch always
points to the latest release, so it's constantly rebasing.

http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary

To develop on top of mmotm git:

  $ git remote add mmotm 
git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
  $ git remote update mmotm
  $ git checkout -b topic mmotm/master
  make changes, commit
  $ git send-email mmotm/master.. [...]

To rebase a branch with older patches to a new mmotm release:

  $ git remote update mmotm
  $ git rebase --onto mmotm/master topic base topic




The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
contains daily snapshots of the -mm tree.  It is updated more frequently
than mmotm, and is untested.

A git copy of this tree is available at

http://git.cmpxchg.org/?p=linux-mmots.git;a=summary

and use of this tree is similar to
http://git.cmpxchg.org/?p=linux-mmotm.git, described above.


This mmotm tree contains the following patches against 3.10-rc4:
(patches marked * will be included in linux-next)

  origin.patch
  linux-next.patch
  linux-next-git-rejects.patch
  arch-alpha-kernel-systblss-remove-debug-check.patch
  i-need-old-gcc.patch
* cpu-hotplug-provide-a-generic-helper-to-disable-enable-cpu-hotplug.patch
* cpu-hotplug-provide-a-generic-helper-to-disable-enable-cpu-hotplug-v11.patch
* migrate-shutdown-reboot-to-boot-cpu.patch
* migrate-shutdown-reboot-to-boot-cpu-v11.patch
* kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg.patch
* kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg-fix.patch
* 
lib-mpi-mpicoderc-looping-issue-need-stop-when-equal-to-zero-found-by-extra_flags=-w.patch
* ocfs2-ocfs2_prep_new_orphaned_file-should-return-ret.patch
* memcg-dont-initialize-kmem-cache-destroying-work-for-root-caches.patch
* rtc-tps6586x-device-wakeup-flags-correction.patch
* drivers-rtc-rtc-cmosc-fix-accidentally-enabling-rtc-channel.patch
* drivers-rtc-rtc-cmosc-fix-accidentally-enabling-rtc-channel-fix.patch
* audit-wait_for_auditd-should-use-task_uninterruptible.patch
* cciss-fix-broken-mutex-usage-in-ioctl.patch
* 
drivers-rtc-rtc-twlc-fix-missing-device_init_wakeup-when-booted-with-device-tree.patch
* 
swap-avoid-read_swap_cache_async-race-to-deadlock-while-waiting-on-discard-i-o-completion.patch
* 
fs-ocfs2-nameic-remove-unecessary-error-when-removing-non-empty-directory.patch
* rtc-at91rm9200-add-match-table-compile-guard.patch
* rtc-at91rm9200-add-configuration-support.patch
* rtc-at91rm9200-refactor-interrupt-register-handling.patch
* rtc-at91rm9200-add-shadow-interrupt-mask.patch
* rtc-at91rm9200-use-shadow-imr-on-at91sam9x5.patch
* aio-use-call_rcu-instead-of-synchronize_rcu-in-kill_ioctx.patch
* drivers-misc-sgi-gru-grufilec-fix-info-leak-in-gru_get_config_info.patch
* mm-page_alloc-fix-watermark-check-in-__zone_watermark_ok.patch
* mm-migration-add-migrate_entry_wait_huge.patch
* drivers-base-cpuc-fix-maxcpus-boot-option.patch
* drivers-base-cpuc-fix-maxcpus-boot-option-fix.patch
* kernel-audit_treec-audit_add_tree_rule-protect-rule-from-kill_rules.patch
* frontswap-fix-incorrect-zeroing-and-allocation-size-for-frontswap_map.patch
* mm-memcontrol-fix-lockless-reclaim-hierarchy-iterator.patch
* drivers-platform-x86-intel_ips-convert-to-module_pci_driver.patch
* sound-soc-codecs-si476xc-dont-use-0bnnn.patch
* x86-make-mem=-option-to-work-for-efi-platform.patch
* 
audit-fix-mq_open-and-mq_unlink-to-add-the-mq-root-as-a-hidden-parent-audit_names-record.patch
* kernel-auditfilterc-fixing-build-warning.patch
* kernel-auditfilterc-fix-leak-in-audit_add_rule-error-path.patch

Re: mmotm 2013-06-05-17-24 uploaded

2013-06-05 Thread Stephen Rothwell 
Hi Andrew,

On Wed, 05 Jun 2013 17:26:36 -0700 a...@linux-foundation.org wrote:

   linux-next-git-rejects.patch

We must figure out why you sometimes get rejects that I do not get when I
import your series into a git tree.  However in this case you resolution
is not quite right.  It leaves 2 continue statements in
net/mac80211/iface.c at line 191 which will unconditionally short circuit
the enclosing loop.  The version that will be in linux-next today is
correct (and git did it automatically as part of the merge of the old
linux-next tree).

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au


pgp6hFfBMo28T.pgp
Description: PGP signature

Re: mmotm 2013-06-05-17-24 uploaded (rtc)

2013-06-05 Thread Randy Dunlap 
On 06/05/13 17:26, a...@linux-foundation.org wrote:
 The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
 
http://www.ozlabs.org/~akpm/mmotm/
 
 mmotm-readme.txt says
 
 README for mm-of-the-moment:
 
 http://www.ozlabs.org/~akpm/mmotm/
 

on i386 when CONFIG_PM is not enabled:

drivers/rtc/class.c:339:18: error: lvalue required as unary '' operand

due to:
#define rtc_class_dev_pm_opsNULL



-- 
~Randy
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: mmotm 2013-06-05-17-24 uploaded (ptp_pch)

2013-06-05 Thread Randy Dunlap 
On 06/05/13 17:26, a...@linux-foundation.org wrote:
 The mm-of-the-moment snapshot 2013-06-05-17-24 has been uploaded to
 
http://www.ozlabs.org/~akpm/mmotm/
 
 mmotm-readme.txt says
 
 README for mm-of-the-moment:
 
 http://www.ozlabs.org/~akpm/mmotm/
 

on i386:  when CONFIG_PCI is not enabled:

drivers/ptp/ptp_pch.c:710:1: warning: data definition has no type or storage 
class [enabled by default]
drivers/ptp/ptp_pch.c:710:1: warning: type defaults to 'int' in declaration of 
'module_pci_driver' [-Wimplicit-int]
drivers/ptp/ptp_pch.c:710:1: warning: parameter names (without types) in 
function declaration [enabled by default]
drivers/ptp/ptp_pch.c:701:26: warning: 'pch_driver' defined but not used 
[-Wunused-variable]


-- 
~Randy
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/