mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: HID: hid-sensor-hub: fix sleeping function called from invalid context
Date: Tue, 10 Jun 2014 10:18:38 +0200	[thread overview]
Message-ID: <5396BF5E.7070805@ahsoftware.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1406100038150.2827@pobox.suse.cz>

Am 10.06.2014 00:40, schrieb Jiri Kosina:
> On Tue, 10 Jun 2014, Alexander Holler wrote:
> 
>> Hello,
>>
>> while rebasing the dozens (currently around 60) of refused, ignored or
>> similiar bugfixes and patches I need to use a Linux kernel, I've noticed that
>> Jiri Kosinas patch here
>>
>> https://lkml.org/lkml/2013/8/9/214
>>
>> doesn't apply anymore.
>>
>> Looking why, I've seen that a similiar patch from Srinivas Pandruvada named
>> like the topic ended up in the kernel.
> 
> Hi Alexander,
> 
> thanks for drawing this one from the boulevard of forgotten patches.
> 
> I am actually not aware of any patch by Srinivas that would conflict with 
> the one I've written -- could you please elaborate where you believe the 
> conflict is?

I actually don't rebase from main-version to main-version (that doesn't
really work), but I'm using format-patch and git am. It's a bit more
strict when that's ok. I haven't looked in deep which changes in 3.15 do
conflict with the patch based on 3.14, but it't can't be that much.

>> Looking at the differences, I wonder if not all spin_lock() calls in 
>> hid-sensor-hub.c should be changed into spin_lock_irqsave() like the 
>> patch from Jiri Kosina did.
> 
> Could you please give me your Tested-by:? I'll then be happily queuing the 
> fix. Thanks.

Sure, but I already did that in the reply to your patch.

>> (sorry for the duplicate message, I've forgotten to add the
>> wanna-be-reviewer-school named lkml to the recipients)
> 
> You want to make it to LWN quotes of the week, don't you? :)

No, I'm just too often the object of their first steps and that's why I
won't post any patches on lkml anymore. It might be fun for them to do
reviews on patches from innocent people, but those victims usually don't
share their view. Maybe I will choose full disclosure or similiar I ever
will have an important patch poor Linux users should really have a need for.

Regards,

Alexander Holler

  parent reply	other threads:[~2014-06-10  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 22:21 Alexander Holler
2014-06-09 22:40 ` Jiri Kosina
2014-06-09 23:17   ` Srinivas Pandruvada
2014-06-09 23:19     ` Jiri Kosina
2014-06-10  8:18   ` Alexander Holler [this message]
2014-06-10  9:08     ` Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5396BF5E.7070805@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®