From: greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"noamc@ezchip.com" <noamc@ezchip.com>,
Anton Kolesov <Anton.Kolesov@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARC: gdbserver breakage in Big-Endian configuration #1
Date: Mon, 19 Aug 2013 23:29:01 -0700 [thread overview]
Message-ID: <20130820062901.GA3758@kroah.com> (raw)
In-Reply-To: <5212FCA8.9040204@synopsys.com>
On Tue, Aug 20, 2013 at 10:50:40AM +0530, Vineet Gupta wrote:
> Hi Greg,
>
> On 08/19/2013 08:27 PM, greg Kroah-Hartman wrote:
> > On Mon, Aug 19, 2013 at 09:08:49AM +0000, Vineet Gupta wrote:
> >> Hi Greg,
> >>
> >> I'd posted these patches for stable backport. Do I need to do anything more to get them included.
> >>
> >> https://patchwork.kernel.org/patch/2841153/ [1/2] ARC: gdbserver breakage in Big-Endian configuration #1<https://patchwork.kernel.org/patch/2841153/>]
> >> https://patchwork.kernel.org/patch/2841158/ [2/2] ARC: gdbserver breakage in Big-Endian configuration #2<https://patchwork.kernel.org/patch/2841158/>
> >
> > I ignored them as I thought you were submitting them for upstream
> > inclusion. If they are already in Linus's tree, then take a look at the
> > file, Documentation/stable_kernel_rules.txt for how to send a patch for
> > inclusion into a stable release (hint, I need to know the git commit id
> > that the patch has in Linus's tree, which I didn't see anywhere here.)
>
>
> I'm sure I mentioned the commit-id in the patch. Hint, please look at annotation
> within --->8--- blocks in changelogs.
You're right, I missed that, sorry.
> The caveat however is we can't apply those exact commits as it is as that warrants
> more changes to be pulled in. However I'm going by the last stable kernel rule "It
> or an equivalent fix must already exist in Linus' tree (upstream)."
>
> Anyhow, since both these patches are extracted from same commit, I'll respin a
> single patch (with a small addition - again part of the same commit) and send it
> over. OK !
That would be great, thanks.
greg k-h
next prev parent reply other threads:[~2013-08-20 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 13:52 [PATCH 1/2] ARC: gdbserver breakage in Big-Endian configuration #1 Vineet Gupta
2013-08-08 13:52 ` [PATCH 2/2] ARC: gdbserver breakage in Big-Endian configuration #2 Vineet Gupta
2013-08-19 9:08 ` [PATCH 1/2] ARC: gdbserver breakage in Big-Endian configuration #1 Vineet Gupta
2013-08-19 14:57 ` greg Kroah-Hartman
2013-08-20 5:20 ` Vineet Gupta
2013-08-20 6:29 ` greg Kroah-Hartman [this message]
2013-08-20 8:08 ` [PATCH 0/2] ARC fixes for 3.9/3.10 stable backport Vineet Gupta
2013-08-20 8:08 ` [PATCH 1/2] ARC: gdbserver breakage in Big-Endian configuration #1 Vineet Gupta
2013-08-22 22:37 ` Patch "ARC: gdbserver breakage in Big-Endian configuration #1" has been added to the 3.10-stable tree gregkh
2013-08-20 8:08 ` [PATCH 2/2] ARC: gdbserver breakage in Big-Endian configuration #2 Vineet Gupta
2013-08-22 22:37 ` Patch "ARC: gdbserver breakage in Big-Endian configuration #2" has been added to the 3.10-stable tree gregkh
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=20130820062901.GA3758@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Anton.Kolesov@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noamc@ezchip.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;
as well as URLs for NNTP newsgroup(s).