public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Lee Jones <lee.jones@linaro.org>
Cc: Eduardo Valentin <edubezval@gmail.com>,
	ajitpal.singh@st.com, rui.zhang@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: patch "drivers: thermal: st: remove several sparse warnings" added to thermal-soc tree
Date: Wed, 8 Apr 2015 11:11:54 +0200	[thread overview]
Message-ID: <20150408091154.GB5646@amd> (raw)
In-Reply-To: <20150408072634.GA5162@x1>

On Wed 2015-04-08 08:26:34, Lee Jones wrote:
> On Tue, 07 Apr 2015, Eduardo Valentin wrote:
> 
> > 
> > This is a simple automated notification to let you know that 
> > I've just added the patch titled
> > 
> >     drivers: thermal: st: remove several sparse warnings
> > 
> > to my thermal-soc git tree which can be found at
> >     git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal.git
> > in the fixes branch.
> > 
> > The patch will show up in the next release of the linux-next tree
> > (usually sometime within the next 24 hours during the week.)
> > 
> > The patch will hopefully also be merged in Linus's tree for the
> > next -rc kernel release.
> > 
> > If you have any questions about this process, please let me know.
> > 
> > All the best,
> > 
> > Eduardo Valentin
> > 
> > ----------
> > From 541d529f9845d249d1cb84f1b395e48f0a117e3f Mon Sep 17 00:00:00 2001
> > From: Eduardo Valentin <edubezval@gmail.com>
> > Date: Tue, 7 Apr 2015 13:42:12 -0700
> > Subject: drivers: thermal: st: remove several sparse warnings
> > 
> > Simple patch to make symbols static. Symbols that are not
> > shared with other parts of the kernel can be made static.
> > This change also removes several sparse complains.
> > 
> > Cc: Zhang Rui <rui.zhang@intel.com>
> > Cc: Lee Jones <lee.jones@linaro.org>
> > Cc: Pavel Machek <pavel@ucw.cz>
> > Cc: Ajit Pal Singh <ajitpal.singh@st.com>
> > Cc: linux-pm@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> 
> Hold on a second, you can't do that.
> 
> Adding these Cc: tags means "this person has been given the opportunity
> to comment on the patch but has chosen not to".  However, you've
> applied this patch ~1min after sending it to the lists.

Cc means -- that person was Cced. And there's no harm in having patch
available in git for easy testing.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-04-08  9:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <14284396653168@besouro>
2015-04-08  7:26 ` patch "drivers: thermal: st: remove several sparse warnings" added to thermal-soc tree Lee Jones
2015-04-08  9:11   ` Pavel Machek [this message]
2015-04-08  9:45     ` Lee Jones
2015-04-08  9:59       ` Pavel Machek
2015-04-08 10:16         ` Lee Jones
2015-04-08 10:35           ` Pavel Machek

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=20150408091154.GB5646@amd \
    --to=pavel@ucw.cz \
    --cc=ajitpal.singh@st.com \
    --cc=edubezval@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.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