linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lijun Pan <Lijun.Pan@freescale.com>
Cc: arnd@arndb.de, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, bhamciu1@freescale.com,
	Lijun.Pan2000@gmail.com, bhupesh.sharma@freescale.com,
	german.rivera@freescale.com, agraf@suse.de,
	stuart.yoder@freescale.com, nir.erez@freescale.com,
	itai.katz@freescale.com, scottwood@freescale.com,
	leoli@freescale.com, R89243@freescale.com,
	dan.carpenter@oracle.com, richard.schmitt@freescale.com
Subject: Re: [PATCH RESEND v2 1/8] staging: fsl-mc: static inline function to differentiate root dprc
Date: Sun, 7 Feb 2016 19:34:27 -0800	[thread overview]
Message-ID: <20160208033427.GA29235@kroah.com> (raw)
In-Reply-To: <1449861954-2824-2-git-send-email-Lijun.Pan@freescale.com>

On Fri, Dec 11, 2015 at 01:25:47PM -0600, Lijun Pan wrote:
> Define a static inline function is_root_dprc(dev) to tell whether
> a device is root dprc or not via platform_bus_type.
> Remove fsl_mc_is_root_dprc() because is_root_dprc() is simpler
> and easier to understand.
> 
> Signed-off-by: Lijun Pan <Lijun.Pan@freescale.com>
> ---
> v2: use static inline function instead of macro
>     replace the fsl_mc_is_root_dprc with is_root_dprc


This series doesn't apply to my tree anymore, due to another big
patcheset for this subsystem being applied.  Can you please rebase it
against my staging-testing branch of staging.git and resend?

thanks,

greg k-h

  reply	other threads:[~2016-02-08  3:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 19:25 [PATCH RESEND v2 0/8] Management Complex restool driver Lijun Pan
2015-12-11 19:25 ` [PATCH RESEND v2 1/8] staging: fsl-mc: static inline function to differentiate root dprc Lijun Pan
2016-02-08  3:34   ` Greg KH [this message]
2016-02-09  0:02     ` Lijun Pan
2015-12-11 19:25 ` [PATCH RESEND v2 2/8] staging: fsl-mc: add sysfs rescan attribute in TODO Lijun Pan
2015-12-11 19:25 ` [PATCH RESEND v3 3/8] staging: fsl-mc: dprc device's sysfs rescan documentation Lijun Pan
2015-12-11 19:25 ` [PATCH RESEND v2 4/8] staging: fsl-mc: root dprc rescan attribute to sync kernel with MC Lijun Pan
2015-12-11 19:25 ` [PATCH RESEND v2 5/8] staging: fsl-mc: fsl-mc bus's sysfs rescan documentation Lijun Pan
2015-12-11 19:25 ` [PATCH RESEND v2 6/8] staging: fsl-mc: bus rescan attribute to sync kernel with MC Lijun Pan
2015-12-11 19:25 ` [PATCH RESEND v2 7/8] staging: fsl-mc: update TODO and README for restool driver Lijun Pan
2015-12-11 19:25 ` [PATCH RESEND v2 8/8] staging: fsl-mc: Management Complex " Lijun Pan

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=20160208033427.GA29235@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Lijun.Pan2000@gmail.com \
    --cc=Lijun.Pan@freescale.com \
    --cc=R89243@freescale.com \
    --cc=agraf@suse.de \
    --cc=arnd@arndb.de \
    --cc=bhamciu1@freescale.com \
    --cc=bhupesh.sharma@freescale.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=german.rivera@freescale.com \
    --cc=itai.katz@freescale.com \
    --cc=leoli@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir.erez@freescale.com \
    --cc=richard.schmitt@freescale.com \
    --cc=scottwood@freescale.com \
    --cc=stuart.yoder@freescale.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 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).