headers
Andrew Morton | 1 Mar 2012 01:02

Re: [PATCH] get_maintainer.pl: Add support for moderated lists

On Wed, 29 Feb 2012 21:06:45 +0100
Richard Weinberger <richard <at> nod.at> wrote:

> Am 29.02.2012 20:58, schrieb Joe Perches:
> > <shrug>  From my perspective, it's correct and simple.
> > 
> > Moderated lists just means your email may get delayed
> > and you may get a "delayed due to moderation" email.
> 
> Most moderated lists are "moderated" by nobody and the patch
> goes to /dev/null.

That's a big problem - we don't want people to send their fixes and bug
reports into black holes.

So yes, I think that teaching get_maintainer to emit black hole
warnings is a good idea.

Problem is, I don't think the string "moderated" explains the situation
very well for the uninitiated :(
Permalink | Reply | 4 comments |
headers
Daniel Palmer | 1 Mar 2012 01:03
Picon

Re: at91: SAM9G45 doesn't seem to register HDMAC controller anymore

On Thursday, March 01, 2012 01:36:44 AM Nicolas Ferre wrote:

> Hi,

> So, you can find here:
> 1/ =>
> http://git.kernel.org/?p=linux/kernel/git/arm/arm-soc.git;a=commitdiff;h=bd
> ad0b9a1c7222a771d25e2a20e81f5563968002
> http://git.kernel.org/?p=linux/kernel/git/arm/arm-soc.git;a=commit;h=2756b
> f5c03bd6fec9462c0742dddb771838bf080
> 
> 2/ =>
> http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=43df92914e
> a0623893bcb801791d5d2be2f5e015
> 
> You can "cherry-pick" those patches using git.

I'll do that later on today when I get some free time and report the results. 
Thanks :)

Daniel
Permalink | Reply | 0 comments |
headers
Linus Torvalds | 1 Mar 2012 01:08
Gravatar

Re: [PATCH] Fix setting bio flags in drivers (sd_dif/floppy).

On Wed, Feb 29, 2012 at 3:22 PM, Muthu Kumar <muthu.lkml <at> gmail.com> wrote:
> Fix setting bio flags in drivers (sd_dif/floppy).

A quick grep seems to agree that these are the only obvious ones.

Jens? Will you send this to me, or should I take it directly?

And when did Andrew change his name? Nobody tells me these things.

                        Linus
Permalink | Reply | 2 comments |
headers
Rafael J. Wysocki | 1 Mar 2012 01:13
Picon
Gravatar

Re: [PATCH 2/2] power_supply: Charger-Manager: provide function for in-kernel use

On Thursday, February 23, 2012, Donggeun Kim wrote:
> By using cm_notify_event function,
> charger driver can report several charger events
> (e.g. battery full and external power in/out, etc) to Charger-Manager.
> Charger-Manager can properly and immediately control chargers
> by the reported event.
> 
> Signed-off-by: MyungJoo Ham <myungjoo.ham <at> samsung.com>
> Signed-off-by: Donggeun Kim <dg77.kim <at> samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park <at> samsung.com>
> ---
>  Documentation/power/charger-manager.txt |   16 +++-
>  drivers/power/charger-manager.c         |  157 +++++++++++++++++++++++++++++++
>  include/linux/power/charger-manager.h   |   18 ++++
>  3 files changed, 190 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/power/charger-manager.txt b/Documentation/power/charger-manager.txt
> index 47f7fdc..f6566c7 100644
> --- a/Documentation/power/charger-manager.txt
> +++ b/Documentation/power/charger-manager.txt
>  <at>  <at>  -50,6 +50,10  <at>  <at>  Charger Manager supports the following:
>  	restarts charging. This check is also performed while suspended by
>  	setting wakeup time accordingly and using suspend_again.
>  
> +* Support for uevent-notify
> +	With the charger-related events, the device sends
> +	notification to users with UEVENT.
> +
>  2. Global Charger-Manager Data related with suspend_again
>  ========================================================
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alan Cox | 1 Mar 2012 01:11
Face
Picon

Re: [PATCH 1/3] drivers/misc: add support for BMP18x pressure sensors

On Wed, 29 Feb 2012 20:58:07 +0100
Eric Andersson <eric.andersson <at> unixphere.com> wrote:

> This driver adds support for Bosch Sensortec's pressure sensors
> BMP085 and BMP18x.
> 
> The driver is based on the bmp085 driver by Christoph Mair
> and uses the same sysfs interface.

This is really extending bmp085 to cover the 18x chips. We don't normally
rename everything for that, and you risk breaking existing setups
assuming the module name is bmp085.

So please just "update" the existing driver - ie the code looks fine but
it should still end up being bmp085.

Alan
Permalink | Reply | 0 comments |
headers
Andrew Morton | 1 Mar 2012 01:12

Re: [PATCH] Fix setting bio flags in drivers (sd_dif/floppy).

On Wed, 29 Feb 2012 18:22:14 -0500
Muthu Kumar <muthu.lkml <at> gmail.com> wrote:

> Fix setting bio flags in drivers (sd_dif/floppy).
> 
> ...
> 
> diff --git a/drivers/block/floppy.c b/drivers/block/floppy.c
> index 9baf11e..744f078 100644
> --- a/drivers/block/floppy.c
> +++ b/drivers/block/floppy.c
>  <at>  <at>  -3832,7 +3832,7  <at>  <at>  static int __floppy_read_block_0(struct
> block_device *bdev)
>  	bio.bi_size = size;
>  	bio.bi_bdev = bdev;
>  	bio.bi_sector = 0;
> -	bio.bi_flags = BIO_QUIET;
> +	bio.bi_flags = (1 << BIO_QUIET);
>  	init_completion(&complete);
>  	bio.bi_private = &complete;
>  	bio.bi_end_io = floppy_rb0_complete;
> diff --git a/drivers/scsi/sd_dif.c b/drivers/scsi/sd_dif.c
> index 0cb39ff..f8fb2d6 100644
> --- a/drivers/scsi/sd_dif.c
> +++ b/drivers/scsi/sd_dif.c
>  <at>  <at>  -408,7 +408,7  <at>  <at>  int sd_dif_prepare(struct request *rq, sector_t
> hw_sector, unsigned int sector_s
>  			kunmap_atomic(sdt, KM_USER0);
>  		}
>
(Continue reading)

Permalink | Reply | 6 comments |
headers
Keith Chew | 1 Mar 2012 01:12
Picon

Re: Hang on "echo b > /proc/sysrq-trigger"

Hi Eric

> I would check with your BIOS folks and perhaps play with the kernel
> option.  The most reliable way to peform a reset is to trigger a board
> reset by writing to 0xcf9 or a similar register.  I expect your BIOS
> does that and you can probably get the kernel to do that.  I would
> definitely test to see if you can write to the mostly standard
> 0xcf9 register directly from the kernel and trigger a reset directly.
>
> Once past a reset and with a single cpu all of the failures will be
> happening in the boot path.  So the only possible points of failure
> are in devices that are different between a soft reset and a power on
> reset.
>
> I would check to see if your board perhaps supports post codes or any
> other debugging that will let you see where you are hanging.
>
> It sounds like there is some very rare failure, that is going to be
> a challenge to track down.  I would definitely test more than one
> motherboard to ensure that you can reproduce the problem on more
> than one piece of hardware.  Sometimes hardware is just broken.
>

These are really helpful suggestions, I will try to get to the bottom
on it. Yes, have tried 3 different boards with different RAM, HDD and
CPU. The hang can be reproduced consistently (just not
deterministically at this stage).

Thank you very much again, will update the progress in due course.
(Continue reading)

Permalink | Reply | 5 comments |
headers
H. Peter Anvin | 1 Mar 2012 01:13
Favicon

Re: [RESUBMIT] [PATCH] Use BIOS Keyboard variable to set Numlock

On 02/29/2012 03:51 PM, Joshua C. wrote:
> 
> Will this work?
> 
> +#if (defined(__i386__) || defined(__x86_64__))
> +#include <asm/io.h>
> +#include <asm/setup.h>
> +#else
> +extern struct boot_params boot_params;
> +#endif
> 

A much better way to do this is probably something like

#ifdef CONFIG_X86

#include <asm/setup.h>

static inline int kbd_defleds(void)
{
	return boot_param.kbd_status & 0x20 ? (1 << VC_NUMLOCK) : 0;
}

#elif defined(CONFIG_PARISC)
static inline int kbd_defleds(void)
{
# if defined(CONFIG_KEYBOARD_HIL) || defined(CONFIG_KEYBOARD_HIL_OLD)
	return 1 << VC_NUMLOCK;
# else
	return 0;
(Continue reading)

Permalink | Reply | 4 comments |
headers
Joshua C. | 1 Mar 2012 01:21

Re: [RESUBMIT] [PATCH] Use BIOS Keyboard variable to set Numlock

2012/3/1 H. Peter Anvin <hpa <at> zytor.com>:
> On 02/29/2012 03:51 PM, Joshua C. wrote:
>>
>> Will this work?
>>
>> +#if (defined(__i386__) || defined(__x86_64__))
>> +#include <asm/io.h>
>> +#include <asm/setup.h>
>> +#else
>> +extern struct boot_params boot_params;
>> +#endif
>>
>
> A much better way to do this is probably something like
>
> #ifdef CONFIG_X86
>
> #include <asm/setup.h>
>
> static inline int kbd_defleds(void)
> {
>        return boot_param.kbd_status & 0x20 ? (1 << VC_NUMLOCK) : 0;
> }
>
> #elif defined(CONFIG_PARISC)
> static inline int kbd_defleds(void)
> {
> # if defined(CONFIG_KEYBOARD_HIL) || defined(CONFIG_KEYBOARD_HIL_OLD)
>        return 1 << VC_NUMLOCK;
> # else
(Continue reading)

Permalink | Reply | 3 comments |
headers
Andrew Morton | 1 Mar 2012 01:20

Re: [PATCH] Fix setting bio flags in drivers (sd_dif/floppy).

On Wed, 29 Feb 2012 16:08:15 -0800
Linus Torvalds <torvalds <at> linux-foundation.org> wrote:

> On Wed, Feb 29, 2012 at 3:22 PM, Muthu Kumar <muthu.lkml <at> gmail.com> wrote:
> > Fix setting bio flags in drivers (sd_dif/floppy).
> 
> A quick grep seems to agree that these are the only obvious ones.
> 
> Jens? Will you send this to me, or should I take it directly?

I'll send at you tomorrowish.  Or you can take it directly, after fixing
the wordwrapping ;)

I don't know if a -stable backport is warranted...

> And when did Andrew change his name? Nobody tells me these things.

oh gawd no.  Somehow google managed to replace my name with my son's in
various people's address books.  Now it's gone and done it with
akpm <at> linux-foundation.org as well as akpm <at> google.com.  I'm in a losing
fight trying to prevent those two identities from getting intermingled,
absorbed and generally borgified.  And how did google know that we're
related?  I can only think that it snarfed that connection from
facebook.
Permalink | Reply | 0 comments |

Gmane