From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Hiro Sugawara <hsugawara-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] iommu/tegra: smmu: Fix deadly typo
Date: Thu, 25 Oct 2012 18:03:28 +0200 [thread overview]
Message-ID: <20121025160328.GC3074@8bytes.org> (raw)
In-Reply-To: <20121025154136.GA30431-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
On Thu, Oct 25, 2012 at 08:41:36AM -0700, Greg KH wrote:
> On Thu, Oct 25, 2012 at 09:06:02AM +0300, Hiroshi Doyu wrote:
> > Putting stable@ on To:. The original ptach attached.
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
>
> </formletter>
I added the stable-tag to the patch before sending it upstream. So I
think it should end up in the stable-kernel soon.
Joerg
prev parent reply other threads:[~2012-10-25 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 5:35 [PATCH 1/1] iommu/tegra: smmu: Fix deadly typo Hiroshi Doyu
[not found] ` <1350538510-28356-1-git-send-email-hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-10-18 15:56 ` Stephen Warren
2012-10-24 15:01 ` Joerg Roedel
[not found] ` <20121024150121.GA2764-5C7GfCeVMHo@public.gmane.org>
2012-10-25 6:06 ` Hiroshi Doyu
[not found] ` <20121025090602.6361b51a5c334bf0009af006-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-10-25 15:41 ` Greg KH
[not found] ` <20121025154136.GA30431-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-10-25 16:03 ` Joerg Roedel [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=20121025160328.GC3074@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=hsugawara-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).