All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Raj Sarraf <rrs@debian.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, debian-kernel@lists.debian.org,
	Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH] um: Don't hardcode path as it is architecture dependent
Date: Tue, 14 May 2019 16:36:38 +0530	[thread overview]
Message-ID: <ae549525ebe4075c9598d8598d39e7d3d088878a.camel@debian.org> (raw)
In-Reply-To: <20190514102645.GA6845@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

Hello Greg,

On Tue, 2019-05-14 at 12:26 +0200, Greg KH wrote:
> On Tue, May 14, 2019 at 03:46:57PM +0530, Ritesh Raj Sarraf wrote:
> > The current code fails to run on amd64 because of hardcoded
> > reference to
> > i386
> > 
> > Signed-off-by: Ritesh Raj Sarraf <rrs@researchut.com>
> > Signed-off-by: Richard Weinberger <richard@nod.at>
> > ---
> >   arch/um/drivers/port_user.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> What is the git commit id of this patch in Linus's tree?

The git commit id should be: 9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed
The web url is: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-05-14 11:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 10:16 [PATCH] um: Don't hardcode path as it is architecture dependent Ritesh Raj Sarraf
2019-05-14 10:26 ` Greg KH
2019-05-14 11:06   ` Ritesh Raj Sarraf [this message]
2019-05-14 12:18     ` Greg KH

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=ae549525ebe4075c9598d8598d39e7d3d088878a.camel@debian.org \
    --to=rrs@debian.org \
    --cc=debian-kernel@lists.debian.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.org \
    /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.