mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Subject: [PATCH-for-next 0/2] move umode_t typedef from asm/types.h to
Date: Mon, 14 Jan 2019 23:06:38 +0300	[thread overview]
Message-ID: <20190114200641.4242-1-antonynpavlov@gmail.com> (raw)

This patchseries is marked "for-next" because it contains
arch/riscv changes.

Antony Pavlov (2):
  MIPS: asm/types.h: drop unused stuff
  move umode_t typedef from asm/types.h to linux/types.h

 arch/arm/include/asm/types.h      |  2 --
 arch/blackfin/include/asm/types.h |  2 --
 arch/mips/include/asm/types.h     | 35 -------------------------------
 arch/nios2/include/asm/types.h    |  2 --
 arch/openrisc/include/asm/types.h |  2 --
 arch/ppc/include/asm/types.h      |  2 --
 arch/riscv/include/asm/types.h    |  2 --
 arch/sandbox/include/asm/types.h  |  2 --
 arch/x86/include/asm/types.h      |  2 --
 include/linux/types.h             |  1 +
 10 files changed, 1 insertion(+), 51 deletions(-)

-- 
2.20.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2019-01-14 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 20:06 Antony Pavlov [this message]
2019-01-14 20:06 ` [PATCH-for-next 1/2] MIPS: asm/types.h: drop unused stuff Antony Pavlov
2019-01-14 20:06 ` [PATCH-for-next 2/2] move umode_t typedef from asm/types.h to linux/types.h Antony Pavlov
2019-01-16  7:37 ` [PATCH-for-next 0/2] move umode_t typedef from asm/types.h to Sascha Hauer

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=20190114200641.4242-1-antonynpavlov@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox