public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Benjamin Romer <benjamin.romer@unisys.com>,
	David Kershner <david.kershner@unisys.com>,
	devel@driverdev.osuosl.org, sparmaintainer@unisys.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: unisys: remove unused variable
Date: Sun, 8 Feb 2015 16:31:07 +0530	[thread overview]
Message-ID: <20150208110107.GA4091@sudip-PC> (raw)
In-Reply-To: <20150207092216.GB21816@kroah.com>

On Sat, Feb 07, 2015 at 05:22:16PM +0800, Greg Kroah-Hartman wrote:
> On Fri, Feb 06, 2015 at 06:13:21PM +0530, Sudip Mukherjee wrote:
> > we were getting lots of warnings about _tempresult set but not used.
> > _tempresult was used in the macro ISSUE_IO_VMCALL_POSTCODE_SEVERITY
> > which was again using another macro ISSUE_IO_EXTENDED_VMCALL.
> > but the vallue assigned to it was never used.
> > 
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> 
> Your From: address, and this address don't match, so I can't take this
> :(

all my patches have been like this way, and you have taken them before :)
the reason its like this way - (already discussed with Dan Carpenter, reference https://lkml.org/lkml/2014/9/3/473)

we have strict DMARC check for the corporate mail server. DMARC = domain based message authentication.
So the mail i sent reached all the list subscriber from a different server than our designated server,
and as a result it is marked as spam in many places and I have already received a few complaints regarding that.

so at https://lkml.org/lkml/2014/9/3/535 Dan said its ok for him, but depends on you if you want to accept.
And since you have accepted all my patches before so i thought it is ok with you.

if you want I can add an extra From: line, but Dan has already given his commments for that at https://lkml.org/lkml/2014/9/3/135
quoting him :

"If everyone starts using From headers like this then it becomes a pain to deal with."

please let me know how you want me to send the patches if different email address is a problem. I thought different name is a problem, but different email address???

> 
> Fix that up please and resend.
> 
> Also, what tool generated those warnings?
just make W=1 will give these warnings.

regards
sudip
> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2015-02-08 11:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 12:43 [PATCH 1/2] staging: unisys: remove unused variable Sudip Mukherjee
2015-02-06 12:43 ` [PATCH 2/2] staging: unisys: fix directory warning Sudip Mukherjee
2015-02-07  9:21   ` Greg Kroah-Hartman
2015-02-07  9:22   ` Greg Kroah-Hartman
2015-02-07  9:22 ` [PATCH 1/2] staging: unisys: remove unused variable Greg Kroah-Hartman
2015-02-08 11:01   ` Sudip Mukherjee [this message]
2015-02-09 21:35     ` Greg Kroah-Hartman
2015-02-10  5:20       ` Sudip Mukherjee
2015-02-10  6:34         ` Greg Kroah-Hartman
2015-02-10  7:03           ` Sudip Mukherjee
2015-02-11 11:34           ` Sudip Mukherjee
  -- strict thread matches above, loose matches on Subject: below --
2015-11-16 14:46 Sudip Mukherjee

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=20150208110107.GA4091@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=benjamin.romer@unisys.com \
    --cc=david.kershner@unisys.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparmaintainer@unisys.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