From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, weiyongjun1@huawei.com
Subject: Re: FAILED: patch "[PATCH] rtlwifi: Fix kernel oops introduced with commit e49656147359" failed to apply to 4.9-stable tree
Date: Tue, 10 Jan 2017 07:35:19 +0200 [thread overview]
Message-ID: <87eg0btr3c.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <6bfeed2c-31fa-7524-1bb8-be71ecc79b0c@lwfinger.net> (Larry Finger's message of "Mon, 9 Jan 2017 16:40:53 -0600")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> On 01/09/2017 02:04 PM, Greg KH wrote:
>> On Mon, Jan 09, 2017 at 08:30:42PM +0200, Kalle Valo wrote:
>>>
>>> Ah, ok. I'm actually having similar problems and planning to come up
>>> with a some sort of web page which would show what was the first Linux
>>> release to contain the commit. (git-describe doesn't tell that and AFAIK
>>> there is no other git command to show it.) If only I had more free time :)
>>
>> git describe --contains
>
> Greg,
>
> Thanks for that info. Now, all we have to do is remember to run the
> command on mainline rather than our development branches.
I'm still planning to implement some sort of user friendly service for
this, thanks to Greg the implementation just got a lot easier. I'm
thinking of at least showing the first release it was included in (like
in this case v4.10-rc1) but also the trees where the patch is currently.
This way you and me don't need to remember anything, except the url
where to find it :)
--
Kalle Valo
prev parent reply other threads:[~2017-01-10 5:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 12:20 FAILED: patch "[PATCH] rtlwifi: Fix kernel oops introduced with commit e49656147359" failed to apply to 4.9-stable tree gregkh
2017-01-09 14:40 ` Kalle Valo
2017-01-09 17:19 ` Larry Finger
2017-01-09 18:30 ` Kalle Valo
2017-01-09 20:04 ` Greg KH
2017-01-09 20:39 ` Kalle Valo
2017-01-09 22:40 ` Larry Finger
2017-01-10 5:35 ` Kalle Valo [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=87eg0btr3c.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=weiyongjun1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.