public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jasonbstubbs@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform: fix samsung brightness min/max calculations
Date: Mon, 20 Jun 2011 07:36:29 +1000	[thread overview]
Message-ID: <201106200736.29259.jasonbstubbs@gmail.com> (raw)
In-Reply-To: <20110613235549.GA14762@kroah.com>

On Tue, 14 Jun 2011 09:55:49 Greg KH wrote:
> On Fri, May 13, 2011 at 08:44:25PM +1000, Jason Stubbs wrote:
> > As far as I can tell, the patches aren't applied to any trees yet and are
> > just sitting in .../gregkh/patches.git. If that's the case, what I would
> > like is for fix-samsung-brightness-min-max-calculations.patch to be
> > replaced with the version in https://lkml.org/lkml/2011/4/20/1 and I
> > resubmit a fixed (and enhanced)
> > add-support-for-samsung-nc210-nc110.patch that applies on top of it.
> > That way an enhancement patch won't hold up a bugfix patch should there
> > be any further issues.
> 
> Ok, I'll drop this one, but can you resend the above referenced patch so
> I can apply it?

Somehow I managed to screw things up again as the nc210-nc110 patch isn't
against the min-max-calculations patch... Doesn't matter though. The patch I
just resent applies on top of the nc210-nc110 patch that you already have in
patches.git.

> Sorry for the delay in working on this, my access to a samsung laptop is
> now gone, and I've been swamped with other stuff.

No problem.

> Any chance you want to take over maintaining this driver now yourself?
> You seem to have a much better understanding of it in places than I do
> at the moment, combined with a strong need to keep it working properly

I'm not exactly sure what that entails, but I don't have access to any specs
and have never dealt with any hardware programming before. Even these patches
don't directly deal with the hardware so I'm not sure that I'm best suited to
being the maintainer. Having said that, I'm happy to try my hand at any bugs
that arise and review any patches..

Regards,
Jason Stubbs

  parent reply	other threads:[~2011-06-19 21:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  3:58 [PATCH] platform: fix samsung brightness min/max calculations Jason Stubbs
2011-04-28  8:55 ` Jason Stubbs
2011-05-10 22:39   ` Greg KH
2011-05-11  4:47     ` Jason Stubbs
2011-05-11 13:51       ` Greg KH
2011-05-12  2:13         ` Jason Stubbs
2011-05-12 16:44           ` Greg KH
2011-05-13 10:44             ` Jason Stubbs
2011-05-13 10:47               ` [PATCH] platform: add support for samsung nc210/nc110 Jason Stubbs
2011-06-13 23:55               ` [PATCH] platform: fix samsung brightness min/max calculations Greg KH
2011-06-19 21:23                 ` [PATCH] platform: samsung_laptop: " Jason Stubbs
2011-06-19 21:36                 ` Jason Stubbs [this message]
2011-08-24 23:11                   ` [PATCH] platform: " Greg KH
2011-05-12  2:32         ` Jason Stubbs

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=201106200736.29259.jasonbstubbs@gmail.com \
    --to=jasonbstubbs@gmail.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --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