From: Richard Purdie <rpurdie@rpsys.net>
To: Dmitry Baryshkov <dbaryshkov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: make sure led->trigger is valid before calling trigger->activate
Date: Wed, 25 Jun 2008 11:18:22 +0100 [thread overview]
Message-ID: <1214389102.5211.25.camel@dax.rpnet.com> (raw)
In-Reply-To: <20080625095046.GB6950@doriath.ww600.siemens.net>
On Wed, 2008-06-25 at 13:50 +0400, Dmitry Baryshkov wrote:
> On Tue, Jun 24, 2008 at 02:02:35PM -0700, Andrew Morton wrote:
> >
> > The changelog tells us what the patch does, but it doesn't tell us
> > why it does it.
> >
> > This matters. For a start, there is no way in which I (at least)
> > am able to determine whether this change is needed in 2.6.26 nor
> > in 2.6.25.x.
>
> I hope this is better. This isn't an 2.6.25.x material. And probably not
> an 2.6.26.
>
> From 4ce3598c6ce5e6b529a05432b18996a99cc5bf0d Mon Sep 17 00:00:00 2001
> From: Dmitry Baryshkov <dbaryshkov@gmail.com>
> Date: Wed, 25 Jun 2008 13:48:07 +0400
> Subject: [PATCH] leds: make sure led->trigger is valid before calling trigger->activate
>
> This is necessary if one wants to use the led->trigger field during
> trigger activation for a led (e.g. to set up the state of the led).
> No current drivers depend on this.
I seem to remember actively making the code work the way it does when I
originally wrote it, what I can't remember is why I did that :/.
Anyhow, I have no objections to the change and will probably queue it
for the next merge window, its post 2.6.26 material.
Cheers,
Richard
prev parent reply other threads:[~2008-06-25 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 11:48 Dmitry Baryshkov
2008-06-22 17:00 ` Dmitry Baryshkov
2008-06-24 21:02 ` Andrew Morton
2008-06-25 9:50 ` Dmitry Baryshkov
2008-06-25 10:18 ` Richard Purdie [this message]
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=1214389102.5211.25.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=akpm@linux-foundation.org \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®