Geert Uytterhoeven | 21 Dec 12:06 2014

[PATCH] fs/affs: Fix casting in printed messages

  - "inode.i_ino" is "unsigned long",
  - "loff_t" is always "unsigned long long",
  - "sector_t" should be cast to "unsigned long long" for printing,
  - "u32" should not be cast to "unsigned int" for printing.

Signed-off-by: Geert Uytterhoeven <geert <at> linux-m68k.org>
---
 fs/affs/amigaffs.c |  6 +++---
 fs/affs/dir.c      |  8 +++-----
 fs/affs/file.c     | 36 ++++++++++++++++++------------------
 fs/affs/inode.c    |  5 ++---
 fs/affs/namei.c    | 18 +++++++-----------
 5 files changed, 33 insertions(+), 40 deletions(-)

diff --git a/fs/affs/amigaffs.c b/fs/affs/amigaffs.c
index c852f2fa17102a24..511ab6b126183ef8 100644
--- a/fs/affs/amigaffs.c
+++ b/fs/affs/amigaffs.c
 <at>  <at>  -30,7 +30,7  <at>  <at>  affs_insert_hash(struct inode *dir, struct buffer_head *bh)
 	ino = bh->b_blocknr;
 	offset = affs_hash_name(sb, AFFS_TAIL(sb, bh)->name + 1, AFFS_TAIL(sb, bh)->name[0]);

-	pr_debug("%s(dir=%u, ino=%d)\n", __func__, (u32)dir->i_ino, ino);
+	pr_debug("%s(dir=%lu, ino=%d)\n", __func__, dir->i_ino, ino);

 	dir_bh = affs_bread(sb, dir->i_ino);
 	if (!dir_bh)
 <at>  <at>  -80,8 +80,8  <at>  <at>  affs_remove_hash(struct inode *dir, struct buffer_head *rem_bh)
 	sb = dir->i_sb;
 	rem_ino = rem_bh->b_blocknr;
(Continue reading)

Geert Uytterhoeven | 21 Dec 12:02 2014

[PATCH selftest fails!] m68k: Wire up execveat

Check success of execveat(3, '../execveat', 0)... [OK]
Check success of execveat(5, 'execveat', 0)... [OK]
Check success of execveat(6, 'execveat', 0)... [OK]
Check success of execveat(-100, '/root/selftest-exec/exec/execveat', 0)... [OK]
Check success of execveat(99, '/root/selftest-exec/exec/execveat', 0)... [OK]
Check success of execveat(8, '', 4096)... [OK]
Check success of execveat(17, '', 4096)... [OK]
Check success of execveat(9, '', 4096)... [OK]
Check success of execveat(14, '', 4096)... [OK]
Check success of execveat(14, '', 4096)... [OK]
Check success of execveat(15, '', 4096)... [OK]
Check failure of execveat(8, '', 0) with ENOENT... [OK]
Check failure of execveat(8, '(null)', 4096) with EFAULT... [OK]
Check success of execveat(5, 'execveat.symlink', 0)... [OK]
Check success of execveat(6, 'execveat.symlink', 0)... [OK]
Check success of execveat(-100, '/root/selftest-exec/...xec/execveat.symlink', 0)... [OK]
Check success of execveat(10, '', 4096)... [OK]
Check success of execveat(10, '', 4352)... [OK]
Check failure of execveat(5, 'execveat.symlink', 256) with ELOOP... [OK]
Check failure of execveat(6, 'execveat.symlink', 256) with ELOOP... [OK]
Check failure of execveat(-100, '/root/selftest-exec/exec/execveat.symlink', 256) with ELOOP... [OK]
Check success of execveat(3, '../script', 0)... [OK]
Check success of execveat(5, 'script', 0)... [OK]
Check success of execveat(6, 'script', 0)... [OK]
Check success of execveat(-100, '/root/selftest-exec/exec/script', 0)... [OK]
Check success of execveat(13, '', 4096)... [OK]
Check success of execveat(13, '', 4352)... [OK]
Check failure of execveat(18, '', 4096) with ENOENT... [OK]
Check failure of execveat(7, 'script', 0) with ENOENT... [OK]
Check success of execveat(16, '', 4096)... [OK]
(Continue reading)

Joe Perches | 17 Dec 21:58 2014

rfc: remove early_printk from a few arches? (blackfin, m68k, mips)

It seems like early_printk can be configured into
a few architectures but also appear not to be used.

$ git grep -w "early_printk"
arch/arm/kernel/Makefile:obj-$(CONFIG_EARLY_PRINTK)	+= early_printk.o
arch/arm/kernel/early_printk.c: *  linux/arch/arm/kernel/early_printk.c
arch/arm/mach-socfpga/socfpga.c:	early_printk("Early printk initialized\n");
arch/blackfin/kernel/Makefile:obj-$(CONFIG_EARLY_PRINTK)           += early_printk.o
arch/blackfin/kernel/bfin_dma.c:#include <asm/early_printk.h>
arch/blackfin/kernel/early_printk.c: * derived from arch/x86/kernel/early_printk.c
arch/blackfin/kernel/early_printk.c:#include <asm/early_printk.h>
arch/blackfin/kernel/setup.c:#include <asm/early_printk.h>
arch/blackfin/kernel/shadow_console.c:#include <asm/early_printk.h>
arch/blackfin/mm/init.c:#include <asm/early_printk.h>
arch/ia64/sn/kernel/setup.c:	 * IO on SN2 is done via SAL calls, early_printk won't work without this.
arch/m68k/kernel/Makefile:obj-$(CONFIG_EARLY_PRINTK)	+= early_printk.o
arch/microblaze/kernel/Makefile:obj-$(CONFIG_EARLY_PRINTK)	+= early_printk.o
arch/microblaze/kernel/cpu/cpuinfo-pvr-full.c:	early_printk("ERROR: Microblaze " x "-different
for PVR and DTS\n");
arch/microblaze/kernel/cpu/cpuinfo-static.c:	early_printk("ERROR: Microblaze " x "-different
for kernel and DTS\n");
arch/microblaze/kernel/setup.c:/* initialize device tree for usage in early_printk */
arch/mips/ath25/Makefile:obj-$(CONFIG_EARLY_PRINTK) += early_printk.o
arch/mips/ath79/Makefile:obj-$(CONFIG_EARLY_PRINTK)		+= early_printk.o
arch/mips/bcm63xx/Makefile:obj-$(CONFIG_EARLY_PRINTK)	+= early_printk.o
arch/mips/include/asm/mach-lantiq/falcon/lantiq_soc.h: * during early_printk no ioremap possible
at this early stage
arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h: * during early_printk no ioremap is possible
arch/mips/kernel/Makefile:obj-$(CONFIG_EARLY_PRINTK)	+= early_printk.o
arch/mips/lantiq/Makefile:obj-$(CONFIG_EARLY_PRINTK) += early_printk.o
(Continue reading)

Masahiro Yamada | 15 Dec 10:32 2014

[Question] How to print size_t type variable?

Hi experts,

I read through Documentation/printk-formats.txt

It clearly says to use "%zu" or "%zx" to print size_t variables,
but I still have a question.

Assume we have code something like:

    printk("%zx", (size_t)10);

I think this code works fine as long as it includes
the compiler-provided <stddef.h>.

In the kernel space, however, <stddef.h> is never included.
Instead, size_t is defined by include/linux/types.h
and include/uapi/asm-generic/posix_types.h.

That is, size_t is defined independently from the compiler you are using,
although the compiler still decides which variable type is expected for the "%zx" format.

This causes compiler warnings for some compilers.

On bare-metal m68k toolchains, for example, size_t is "unsignd long",
whearas it is "unsigned int" on kernel.org m68k toolchains.

I see such warnings when I built the kernel with bare-metal m68k toolchains.

$ git describe 
v3.18
(Continue reading)

Geert Uytterhoeven | 8 Dec 10:52 2014

[git pull] m68k updates for 3.19

	Hi Linus,

The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:

  Linux 3.18-rc2 (2014-10-26 16:48:41 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus

for you to fetch changes up to f0b99a643e9613beb28af43333bbfa90d4bf85cc:

  m68k/mm: Eliminate memset after alloc_bootmem_pages (2014-11-10 09:56:44 +0100)

----------------------------------------------------------------
Geert Uytterhoeven (1):
      nubus: Remove superfluous interrupt disable/restore

Himangi Saraogi (1):
      m68k/mm: Eliminate memset after alloc_bootmem_pages

 arch/m68k/mm/init.c   | 1 -
 drivers/nubus/nubus.c | 4 ----
 2 files changed, 5 deletions(-)

Thanks for pulling!

Gr{oetje,eeting}s,

						Geert
(Continue reading)

Quan Han | 1 Dec 14:02 2014

Re:


Hello,

Compliments of the day to you and I believe all is well. My name is Mr. Quan Han and I work in bank of china. I have
a transaction that I believe will be of mutual benefits to both of us. It involves an investment portfolio
worth(eight million,three hundred and seventy thousand USD) which I like to acquire with your help and
assistance. 
Yours sincerely,
Quan Han.
Michael Schmitz | 30 Nov 19:58 2014
Picon

[PATCH] m68k/atari - smc91x: remove Atari special case handling for SMC_PUSH_DATA

Use of string accessors for unaligned writes (see mainstream commit
e9e4ea74f06635f2ffc1dffe5ef40c854faa0a90) have fixed the swapped
first unaligned byte problem for the Atari EtherNAT. Drop the
redundant special case code now.

Signed-off-by: Michael Schmitz <schmitz <at> debian.org>
Tested-by: Christian Steigies <cts <at> debian.org>
---
 drivers/net/ethernet/smsc/smc91x.h |   37 ------------------------------------
 1 files changed, 0 insertions(+), 37 deletions(-)

diff --git a/drivers/net/ethernet/smsc/smc91x.h b/drivers/net/ethernet/smsc/smc91x.h
index 3a8069f..14c5325 100644
--- a/drivers/net/ethernet/smsc/smc91x.h
+++ b/drivers/net/ethernet/smsc/smc91x.h
 <at>  <at>  -223,8 +223,6  <at>  <at>  SMC_outw(u16 val, void __iomem *ioaddr, int reg)
 #define SMC_CAN_USE_32BIT       1
 #define SMC_NOWAIT              1

-#define writew_be(val, addr) out_be16((addr), (val))
-
 #define SMC_inb(a, r)           readb((a) + (r))
 #define SMC_inw(a, r)           readw((a) + (r))
 #define SMC_inl(a, r)           readl((a) + (r))
 <at>  <at>  -1128,40 +1126,6  <at>  <at>  static const char * chip_ids[ 16 ] =  {
 		}							\
 	} while (0)

-#if defined(CONFIG_ATARI)
-/*
(Continue reading)

Geert Uytterhoeven | 30 Nov 10:30 2014

[PATCH v2 1/2] Input: amikbd - Fix build if !CONFIG_HW_CONSOLE

If CONFIG_HW_CONSOLE is not set:

drivers/built-in.o: In function `amikbd_probe':
amikbd.c:(.init.text+0x3e4e): undefined reference to `key_maps'
amikbd.c:(.init.text+0x3dd4): undefined reference to `key_maps'

To fix this, extract the initialization of the console keyboard maps
into amikbd_init_console_keymaps(), protected by #ifdef
CONFIG_HW_CONSOLE.

Signed-off-by: Geert Uytterhoeven <geert <at> linux-m68k.org>
---
Discovered during randconfig builds.

v2:
  - No changes
---
 drivers/input/keyboard/amikbd.c | 46 ++++++++++++++++++++++++++---------------
 1 file changed, 29 insertions(+), 17 deletions(-)

diff --git a/drivers/input/keyboard/amikbd.c b/drivers/input/keyboard/amikbd.c
index 096d6067ae1f890f..4f81e65d9e35cb7d 100644
--- a/drivers/input/keyboard/amikbd.c
+++ b/drivers/input/keyboard/amikbd.c
 <at>  <at>  -45,6 +45,7  <at>  <at>  MODULE_AUTHOR("Vojtech Pavlik <vojtech <at> ucw.cz>");
 MODULE_DESCRIPTION("Amiga keyboard driver");
 MODULE_LICENSE("GPL");

+#ifdef CONFIG_HW_CONSOLE
 static unsigned char amikbd_keycode[0x78] __initdata = {
(Continue reading)

ceremonials69080 | 25 Nov 17:40 2014
Picon

Fix Penguin Penalty 17th October2014 ( mail-archive.com )

Dear Sir

Did your website get hit by Google Penguin update on October 17th 2014? What basically is Google Penguin
Update? It is actually a code name for Google algorithm which aims at decreasing your websites search
engine rankings that violate Google’s guidelines by using black hat SEO techniques to rank your webpage
by giving number of spammy links to the page.

We are one of those few SEO companies that can help you avoid penalties from Google Updates like Penguin and
Panda. Our clients have survived all the previous and present updates with ease. They have never been hit
because we use 100% white hat SEO techniques to rank Webpages.  Simple thing that we do to keep websites away
from any Penguin or Panda penalties is follow Google guidelines and we give Google users the best answers
to their queries.

If you are looking to increase the quality of your websites and to get more targeted traffic or save your
websites from these Google penalties email us back with your interest. 

We will be glad to serve you and help you grow your business.

Regards

Julia kites

SEO Manager ( TOB )
B7 Green Avenue, Amritsar 143001 Punjab
____________________________
NO CLICK in the subject to STOP EMAILS
indeclinable04913 | 17 Nov 08:53 2014
Picon

Fix Penguin Penalty 17th October2014 ( mail-archive.com )

Dear Sir

Did your website get hit by Google Penguin update on October 17th 2014? What basically is Google Penguin
Update? It is actually a code name for Google algorithm which aims at decreasing your websites search
engine rankings that violate Google’s guidelines by using black hat SEO techniques to rank your webpage
by giving number of spammy links to the page.

We are one of those few SEO companies that can help you avoid penalties from Google Updates like Penguin and
Panda. Our clients have survived all the previous and present updates with ease. They have never been hit
because we use 100% white hat SEO techniques to rank Webpages.  Simple thing that we do to keep websites away
from any Penguin or Panda penalties is follow Google guidelines and we give Google users the best answers
to their queries.

If you are looking to increase the quality of your websites and to get more targeted traffic or save your
websites from these Google penalties email us back with your interest. 

We will be glad to serve you and help you grow your business.

Regards

Vince G

SEO Manager ( TOB )
B7 Green Avenue, Amritsar 143001 Punjab
____________________________
NO CLICK in the subject to STOP EMAILS
mitchellmiller | 13 Nov 06:44 2014
Picon

A recommendation from Mitchell Miller


Hello,

Subject: YOUR Millionaire Money Machine is Here!

Hey Friend,

As you know, I’m always on the lookout for 
real ways to make decent money.       
                                                     
Not just a measly $20 or $30 a day; I mean real money. 

$20,000 or $30,000 A DAY?!?! Now THAT is…

DAMN GOOD REAL MONEY!

His 6 figure bank accounts now are a pretty good 
indicator that Trevor Haynes has figured it out.

Check this out -  http://crossfires.mmmachine.cpa.clicksure.com   

The Millionaire Money Machine has nothing to do with 
eBooks, websites, T-shirts, MLM, gambling, writing, 
flipping sites or any of that.

THIS isn’t about making ten buck here or there. 

It’s about making TENS OF THOUSANDS DAILY.

You’ll meet one Millionaire Money Machine user who 
(Continue reading)


Gmane