All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Tomas Winkler <tomas.winkler@intel.com>,
	Joe Perches <joe@perches.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jiri Kosina <jkosina@suse.cz>,
	Sharon Dvir <sharon.dvir1@mail.huji.ac.il>,
	"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	James Hogan <james.hogan@imgtec.com>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Michael Opdenacker <michael.opdenacker@free-electrons.com>,
	David Cohen <david.a.cohen@linux.intel.com>,
	Felipe Balbi <balbi@ti.com>, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] mei, make modules.alias UUID information easier to read
Date: Sun, 20 Sep 2015 19:25:28 -0700	[thread overview]
Message-ID: <20150921022528.GA21281@kroah.com> (raw)
In-Reply-To: <1439557540-1989-1-git-send-email-prarit@redhat.com>

On Fri, Aug 14, 2015 at 09:05:40AM -0400, Prarit Bhargava wrote:
> 2nd try on this ...

What changed from the first patch?  I need some "version information" to
figure out what is going on.

Can you resend it with that information?

thanks,

greg k-h

  parent reply	other threads:[~2015-09-21  4:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 13:05 [PATCH] mei, make modules.alias UUID information easier to read Prarit Bhargava
2015-08-28 11:50 ` Prarit Bhargava
2015-08-28 12:46   ` Heikki Krogerus
2015-08-29 21:21     ` Winkler, Tomas
2015-08-30 17:36       ` Prarit Bhargava
2015-08-31  7:17         ` Winkler, Tomas
2015-09-01  0:09       ` Prarit Bhargava
2015-09-21  2:25 ` Greg Kroah-Hartman [this message]
2015-09-21  8:13   ` Winkler, Tomas
  -- strict thread matches above, loose matches on Subject: below --
2015-08-07 14:06 Prarit Bhargava

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=20150921022528.GA21281@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=balbi@ti.com \
    --cc=daniel.thompson@linaro.org \
    --cc=davem@davemloft.net \
    --cc=david.a.cohen@linux.intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=james.hogan@imgtec.com \
    --cc=jkosina@suse.cz \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=prarit@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=sharon.dvir1@mail.huji.ac.il \
    --cc=tomas.winkler@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.