ALT Linux kernel packages development
 help / color / mirror / Atom feed
From: Vitaly Chikunov <>
To: ALT Linux kernel packages development <>
Subject: Re: [d-kernel] Ядро altlinux-5.18.y с поддержкой СнК Байкал-М
Date: Wed, 6 Jul 2022 12:22:16 +0300
Message-ID: <> (raw)
In-Reply-To: <YsVJAGx74b0jwvfo@asheplyakov-rocket>

On Wed, Jul 06, 2022 at 12:34:08PM +0400, Alexey Sheplyakov wrote:
> Здравствуйте!
> On Thu, Jun 23, 2022 at 02:33:56AM +0300, Vitaly Chikunov wrote:
> > Исходя из этого письма, просмотре списка бранчей и range-diff на них я
> > делаю предположение, что имелся ввиду pull request на
> > 
> > baikalm-5.18.y
> Нет. Поскольку на тот момент в kernel-image-un-def не было ветки на
> основе 5.18, то не понятно, что должно быть базой для pull request.

Любой свежий тэг из stable/linux-5.18.y.

> 5.17.x?

Так как у них разная история, такой pull/merge бы не прошёл.

> А зачем нужен pull request со всеми патчами из mainline
> (между 5.17 и 5.18)?

Можно посмотреть какие патчи применяется - например, на тот момент 
baikalm-5.18.y это был 9986470b38ce:

  un-def/sisyphus$ git log --oneline  v5.18.6..baikalm-5.18.y
  9986470b38ce arm64: device tree: Baikal-M: fixed CPUs opp_table
  b30d06c11ad8 arm64: device tree: Baikal-M: fixed GPU opp_table
  2b00d23106d4 arm64: device tree: Baikal-M: fixed gpio alias
  5aeeb64da9cd arm64: device tree: Baikal-M: fixed PHY binding description
  c0811e9632c2 arm64: device tree: baikal: mark GPU as dma-coherent
  cff31ebc0cd5 arm64: added Baikal-M SoC and TF307 board device tree
  11f6dc033abe arm64: defconfig for Baikal-M testing
  62ae77166939 input: added TF307 serio PS/2 emulator driver
  54f79fda08ff (BROKEN) dwc-i2s: support Baikal-M SoC
  8a359cd36da7 ALSA: hda: Baikal-M support
  9e3e0f907b41 drm/panfrost: disable devfreq on Baikal-M
  d3312983e1f9 drm/panfrost: forcibly set dma-coherent on Baikal-M
  e4348ab6bbe5 drm: dw-hdmi-ahb-audio: support Baikal-M SoC
  4350896b9633 drm: added Baikal-M SoC video display unit driver
  bb8ce38ef3b7 drm: new bridge driver - stdp4028
  4dceca4785ff hwmon: bt1-pvt: added compatible baikal,pvt
  6f38d82abef8 hwmon: bt1-pvt: adjusted probing for Baikal-M SoC
  df40a4afe5b3 hwmon: bt1-pvt: define pvt_readl/pvt_writel for Baikal-M SoC
  b7ebb0ad3830 hwmon: bt1-pvt: access registers via pvt_{readl,writel} helpers
  c5a88c513417 Added TF307/TF306 board management controller driver
  b74818e1e8f9 net: dwmac-baikal: added compatible strings...
  e6bd9ab2fe8d net: stmmac: custom mdio reset for some Baikal-M boards
  49cb520cee2b dt-bindings: dwmac: Add bindings for Baikal-T1/M SoCs
  f7b50a74d6fe net: stmmac: inital support of Baikal-T1/M SoCs GMAC
  771b2e4da93b net: fwnode_get_phy_id: consider all compatible strings
  07ea607fb4c7 pm: disable all sleep states on Baikal-M based boards
  8846921cd2d1 arm64-stub: fixed secondary cores boot on Baikal-M SoC
  b68ec5e66897 efi-rtc: avoid calling efi.get_time on Baikal-M SoC
  7d4317f5d023 arm64: Enable armv8 based Baikal-M SoC support
  31b46701b863 usb: dwc3: of-simple: added compatible string for Baikal-M SoC
  5884a6b01010 [rejected] serial: 8250_dw: verify clock rate in dw8250_set_termios
  a2173dc73211 cpufreq-dt: don't load on Baikal-M SoC
  54fe6c2a78b4 clk: added Baikal-M clock management unit driver

Поэтому всё прошло успешно. Такой вывод git log не должен содержать чужих
пачей, наших патчей или пачей из любого бранча (включая mainline) ядра.


> Так что это просто набор патчей, причём не только для поддержки
> Байкал-М ("802d157601ff clk: added Baikal-M clock management unit
> driver" и далее по тексту), но и всё, что было в un-def: AltHa и
> прочий "синдром вахтёра", а именно:
> > 3b76033d69ce AltHa LSM module
> > 08571583d525 Documentation for AltHa LSM
> > 31ce36ce1bb8 kiosk: implement kiosk module
> > 39ce0c62479a Add ability to disable idmapped mounts
> > ecdf02526c27 pci: Enable overrides for missing ACS capabilities (5.6.9+)
> > f2dcadfa4fbf kmod: pass -b option to /sbin/modprobe (by ldv@)
> > 32817f3a9248 get_arg_page: limit argv+env strings size for AT_SECURE programs
> > d84b7d935929 proc: restrict access to /proc/interrupts
> > 9b3fe2245334 Revert "audit: normalize NETFILTER_PKT"
> > eed9be135b1d Revert "Audit: remove unused audit_log_secctx function"
> > b0289ab120aa sysctl: allow CLONE_NEWUSER to be disabled
> > 9ae84fbcac65 kernel/user_namespace.c: enable CLONE_NEWUSER restriction by default
> > 9eaaa64670b8 Add support for debian-specific kernel.unprivileged_userns_clone parameter
> _______________________________________________
> devel-kernel mailing list

      reply	other threads:[~2022-07-06  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 18:19 Alexey Sheplyakov
2022-06-22 23:33 ` Vitaly Chikunov
2022-07-06  8:34   ` Alexey Sheplyakov
2022-07-06  9:22     ` Vitaly Chikunov [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux kernel packages development

This inbox may be cloned and mirrored by anyone:

	git clone --mirror devel-kernel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel-kernel devel-kernel/ \
	public-inbox-index devel-kernel

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone