linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: devel@driverdev.osuosl.org,
	Sirnam Swetha <theonly.ultimate@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Willy Tarreau <willy@meta-x.org>,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: Re: [PATCH] Revert "Staging: panel: usleep_range is preferred over udelay"
Date: Tue, 26 Jan 2016 04:36:33 +0300	[thread overview]
Message-ID: <20160126013633.GK5325@mwanda> (raw)
In-Reply-To: <87mvrt9o3z.fsf@yhuang-dev.intel.com>

On Tue, Jan 26, 2016 at 08:32:48AM +0800, Huang, Ying wrote:
> Dan Carpenter <dan.carpenter@oracle.com> writes:
> 
> > On Mon, Jan 25, 2016 at 03:13:21PM +0530, Sudip Mukherjee wrote:
> >> Apart from the mail which Ying Huang sent to me last week for another error
> >> (which actually turned out to be this one), i saw the first report by
> >> Ying Huang on November.
> >> https://lkml.org/lkml/2015/11/2/93
> >
> > Ying, could you CC the subsystem list for these reports?  This one was
> > CC'd to Sirnam, Greg and LKML.  Sirnam is too new to understand what
> > they mean, Greg is too busy, and only Sudip and Alan Cox read LKML.
> 
> Sure.  But what is the best way to find the subsystem list for a patch?
> Now we use author, committer, and the xxx-by: and Cc: list in patch to
> find the recipient.

For this one it's simple.  Get the filename from the git commit and
use ./scripts/get_maintainer.pl -f $file.  That should work generally,
the only issue is maybe some patches affect things across subsystems.

Also I don't know if netdev wants these emails?  Do you guys CC them on
0day warnings?

regards,
dan carpenter

  reply	other threads:[~2016-01-26  1:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-23  9:19 [PATCH] Revert "Staging: panel: usleep_range is preferred over udelay" Sudip Mukherjee
2016-01-25  4:36 ` Sudip Mukherjee
2016-01-25  9:16 ` Dan Carpenter
2016-01-25  9:34   ` Dan Carpenter
2016-01-25  9:43   ` Sudip Mukherjee
2016-01-25 11:03     ` Dan Carpenter
2016-01-25 12:40     ` Dan Carpenter
2016-01-25 12:49       ` Sudip Mukherjee
2016-01-25 20:42         ` Willy Tarreau
2016-01-26  0:32       ` Huang, Ying
2016-01-26  1:36         ` Dan Carpenter [this message]
2016-01-26  2:01           ` Huang, Ying
2016-01-25 12:47   ` Joe Perches
2016-01-25 12:51     ` Sudip Mukherjee
2016-01-25 12:58       ` Joe Perches

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=20160126013633.GK5325@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=theonly.ultimate@gmail.com \
    --cc=willy@meta-x.org \
    --cc=ying.huang@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;
as well as URLs for NNTP newsgroup(s).