linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vabhav Sharma <vabhav.sharma@nxp.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PATCHES MERGE MISSING FROM PATCHSET
Date: Wed, 13 Feb 2019 15:13:29 +0100	[thread overview]
Message-ID: <20190213141329.GA10202@kroah.com> (raw)
In-Reply-To: <VI1PR04MB4800E4DAD4729CBA3A146E36F3660@VI1PR04MB4800.eurprd04.prod.outlook.com>

On Wed, Feb 13, 2019 at 02:05:13PM +0000, Vabhav Sharma wrote:
> ++ Kernel Mailing list
> 
> From: Vabhav Sharma
> Sent: Wednesday, February 13, 2019 7:30 PM
> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>; Stephen Boyd <sboyd@kernel.org>; Viresh Kumar <viresh.kumar@linaro.org>
> Subject: PATCHES MERGE MISSING FROM PATCHSET
> Importance: High
> 
> Hello Maintainers,
> I had sent patch series with subject "arm64: dts: NXP: add basic dts file for LX2160A SoC" in 2018.
> *        This is to update you that all the dts and SoC/Board support patches are merged but below two patches are not yet merged from this patchset series.
> *        clk: qoriq: increase array size of cmux_to_group<https://patchwork.kernel.org/patch/10658885/>
> *        clk: qoriq: Add clockgen support for lx2160a<https://patchwork.kernel.org/patch/10658871/>
> Kindly help to merge the patches.

If patches somehow get dropped, just resend them and be sure to cc: the
proper developers/maintainers/lists as shown by
scripts/get_maintainer.pl.

thanks,

greg k-h

           reply	other threads:[~2019-02-13 14:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <VI1PR04MB4800E4DAD4729CBA3A146E36F3660@VI1PR04MB4800.eurprd04.prod.outlook.com>]

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=20190213141329.GA10202@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vabhav.sharma@nxp.com \
    --cc=viresh.kumar@linaro.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).