linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"Xue, Ken" <Ken.Xue@amd.com>,
	"S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] pinctrl/amd: Use regular interrupt instead of chained
Date: Fri, 26 May 2017 11:57:20 +0200	[thread overview]
Message-ID: <20170526095720.lhwcrorqwk2xya2c@pd.tnic> (raw)
In-Reply-To: <BLUPR12MB0721B0824892B985DC807471A0FC0@BLUPR12MB0721.namprd12.prod.outlook.com>

On Fri, May 26, 2017 at 09:33:10AM +0000, Shah, Nehal-bakulchandra wrote:
> Hi Thomas,
> 
> Thanks  for the prompt reply. Agree on points.
> 
> we will validate at our end and shall provide the update.

First of all, please do not top-post.

What update are you talking about? The patch needs to go in regardless.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  reply	other threads:[~2017-05-26  9:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 21:23 [PATCH] pinctrl/amd: Use regular interrupt instead of chained Thomas Gleixner
2017-05-26  4:51 ` Shah, Nehal-bakulchandra
2017-05-26  6:48   ` Thomas Gleixner
2017-05-26  9:33     ` Shah, Nehal-bakulchandra
2017-05-26  9:57       ` Borislav Petkov [this message]
2017-06-19 16:13       ` Borislav Petkov
2017-06-20  9:22         ` Thomas Gleixner
2017-06-20  9:29           ` Borislav Petkov
2017-05-29 11:55 ` Linus Walleij
2017-06-04 13:49   ` Thomas Gleixner
2017-06-20 12:28   ` Borislav Petkov
2017-06-21 16:37     ` Linus Walleij
2017-06-21 17:01       ` Borislav Petkov

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=20170526095720.lhwcrorqwk2xya2c@pd.tnic \
    --to=bp@alien8.de \
    --cc=Ken.Xue@amd.com \
    --cc=Nehal-bakulchandra.Shah@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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).