All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anup Patel <anup@brainfault.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Palmer Dabbelt <palmer@sifive.com>,
	Anup Patel <Anup.Patel@wdc.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Atish Patra <Atish.Patra@wdc.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v3 2/3] RISC-V: Add interrupt related SCAUSE defines in asm/csr.h
Date: Thu, 25 Apr 2019 10:34:16 +0530	[thread overview]
Message-ID: <CAAhSdy0xydwViJW8yCPTLrgkNGjwd4J8P-=4b2P4AfGemmyKyw@mail.gmail.com> (raw)
In-Reply-To: <20190424150135.GA19543@infradead.org>

On Wed, Apr 24, 2019 at 8:31 PM Christoph Hellwig <hch@infradead.org> wrote:
>
> On Wed, Apr 24, 2019 at 12:15:45PM +0530, Anup Patel wrote:
> > We need these defines for programming HIDELEG CSR in KVM kernel module
> > so it will be used at multiple places.
> >
> > >
> > > http://git.infradead.org/users/hch/misc.git/commitdiff/1221f5c32345ebe7ea2c1cd6e8a01ad4b422aaba
> >
> > You can certainly use these defines in your nommu commit by using
> > "#ifdef CONFIG_M_MODE" in switch case of do_IRQ().
>
> Or just keep them in the current format even when you move them, as
> that allows everything to work with a single ifdef at their point
> of declaration..

Sure, will do. I will send v4 soon.

Regards,
Anup

WARNING: multiple messages have this Message-ID (diff)
From: Anup Patel <anup@brainfault.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Palmer Dabbelt <palmer@sifive.com>,
	Anup Patel <Anup.Patel@wdc.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Atish Patra <Atish.Patra@wdc.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v3 2/3] RISC-V: Add interrupt related SCAUSE defines in asm/csr.h
Date: Thu, 25 Apr 2019 10:34:16 +0530	[thread overview]
Message-ID: <CAAhSdy0xydwViJW8yCPTLrgkNGjwd4J8P-=4b2P4AfGemmyKyw@mail.gmail.com> (raw)
In-Reply-To: <20190424150135.GA19543@infradead.org>

On Wed, Apr 24, 2019 at 8:31 PM Christoph Hellwig <hch@infradead.org> wrote:
>
> On Wed, Apr 24, 2019 at 12:15:45PM +0530, Anup Patel wrote:
> > We need these defines for programming HIDELEG CSR in KVM kernel module
> > so it will be used at multiple places.
> >
> > >
> > > http://git.infradead.org/users/hch/misc.git/commitdiff/1221f5c32345ebe7ea2c1cd6e8a01ad4b422aaba
> >
> > You can certainly use these defines in your nommu commit by using
> > "#ifdef CONFIG_M_MODE" in switch case of do_IRQ().
>
> Or just keep them in the current format even when you move them, as
> that allows everything to work with a single ifdef at their point
> of declaration..

Sure, will do. I will send v4 soon.

Regards,
Anup

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-04-25  5:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15  9:37 [PATCH v3 0/3] Allow accessing CSR using CSR number Anup Patel
2019-04-15  9:37 ` Anup Patel
2019-04-15  9:37 ` [PATCH v3 1/3] RISC-V: Use tabs to align macro values in asm/csr.h Anup Patel
2019-04-15  9:37   ` Anup Patel
2019-04-24  6:27   ` Christoph Hellwig
2019-04-24  6:27     ` Christoph Hellwig
2019-04-15  9:37 ` [PATCH v3 2/3] RISC-V: Add interrupt related SCAUSE defines " Anup Patel
2019-04-15  9:37   ` Anup Patel
2019-04-24  6:29   ` Christoph Hellwig
2019-04-24  6:29     ` Christoph Hellwig
2019-04-24  6:45     ` Anup Patel
2019-04-24  6:45       ` Anup Patel
2019-04-24 15:01       ` Christoph Hellwig
2019-04-24 15:01         ` Christoph Hellwig
2019-04-25  5:04         ` Anup Patel [this message]
2019-04-25  5:04           ` Anup Patel
2019-04-15  9:37 ` [PATCH v3 3/3] RISC-V: Access CSRs using CSR numbers Anup Patel
2019-04-15  9:37   ` Anup Patel
2019-04-24  6:30   ` Christoph Hellwig
2019-04-24  6:30     ` Christoph Hellwig

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='CAAhSdy0xydwViJW8yCPTLrgkNGjwd4J8P-=4b2P4AfGemmyKyw@mail.gmail.com' \
    --to=anup@brainfault.org \
    --cc=Anup.Patel@wdc.com \
    --cc=Atish.Patra@wdc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.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.