From: "greg@kroah.com" <greg@kroah.com>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Add support for recent lenovo thinkpad HKEYS(Wifi/video swicth etc) buttons
Date: Wed, 14 Sep 2016 19:08:11 +0200 [thread overview]
Message-ID: <20160914170811.GA13294@kroah.com> (raw)
In-Reply-To: <1473869643.3549.103.camel@infinera.com>
On Wed, Sep 14, 2016 at 04:13:52PM +0000, Joakim Tjernlund wrote:
> On Wed, 2016-09-14 at 16:35 +0200, greg@kroah.com wrote:
> > On Wed, Sep 14, 2016 at 12:00:04PM +0000, Joakim Tjernlund wrote:
> > >
> > > On Wed, 2016-09-14 at 13:54 +0200, Greg KH wrote:
> > > >
> > > > On Wed, Sep 14, 2016 at 06:44:50AM +0000, Joakim Tjernlund wrote:
> > > > >
> > > > >
> > > > > These patches are picked from Linux upstream repo and applies directly on 4.4.x
> > > > > Please excuse the attachments but git send email does not work for us ATM.
> > > >
> > > > What is the git commit ids of these patches in Linus's tree?
> > > 0002-thinkpad_acpi-Add-support-for-keyboard-backlight.patch: 6cf4a2c575b4797b967a575b6274e0e40c5f88f1
> >
> > I do not see that git commit id in Linus's tree, do you?
>
> ehh, no. I used my 4.4 branch instead of linux master, sorry
>
> >
> > >
> > > 0003-thinkpad_acpi-Remove-ambiguous-logging-for-Unsupport.patch: 85342b97c2ee2a94a31ea5d59d58cdfd1f045e2a
> >
> > Nor this one.��I stopped here, assuming that your other ids aren't
> > correct either :(
> >
> > >
> > > 0004-thinkpad_acpi-Silence-an-uninitialized-variable-warn.patch: dcf95a1961f9614eee09066f8148813772ad4268
> > > 0005-thinkpad_acpi-save-kbdlight-state-on-suspend-and-res.patch:1c6c99c6767035761d17aeecaf0224934ccd00fb
> > > 0006-thinkpad_acpi-Add-support-for-HKEY-version-0x200.patch: 1bc0df534d11c8c9c97e1e8315b7d22bf034c8d2
> > > >
> > > >
> > > > And what happened to the other patches in this series?
> > > > �
> > > The first one was inappropriate, that is why 0001 is missing.
> >
> > That's pretty strange of you to force us to guess what is going on here,
> > would you like to get a series like this and wonder why something
> > obvious like this is gone?
>
> Yes, it was inconsiderate of me, sorry.
>
> Trying to do better I figured I should generate a new series from Linus tree but
> I cannot figure out how generate a series from commits that are non sequential in Linux tree.
> git format path does not have a syntax for that from what I can tell, any ideas?
Why not just send us the git commit ids that you want applied? That's
all we need.
thanks,
greg k-h
next prev parent reply other threads:[~2016-09-14 17:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 6:44 Add support for recent lenovo thinkpad HKEYS(Wifi/video swicth etc) buttons Joakim Tjernlund
2016-09-14 11:54 ` Greg KH
2016-09-14 12:00 ` Joakim Tjernlund
2016-09-14 14:35 ` greg
2016-09-14 16:13 ` Joakim Tjernlund
2016-09-14 17:08 ` greg [this message]
2016-09-14 17:57 ` Joakim Tjernlund
2016-09-14 18:10 ` greg
2016-09-14 19:07 ` Joakim Tjernlund
2016-09-15 5:59 ` greg
2016-09-15 8:51 ` Joakim Tjernlund
2016-09-15 10:07 ` greg
2016-09-15 11:57 ` Joakim Tjernlund
2016-09-15 14:31 ` Vasiliy Tolstov
2016-09-15 10:49 ` Vasiliy Tolstov
2016-09-14 11:57 ` Willy Tarreau
2016-09-14 12:05 ` Joakim Tjernlund
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=20160914170811.GA13294@kroah.com \
--to=greg@kroah.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=stable@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